Hey Philippe Couple of things we can do to see what might be going on.
1. Check the port being used by put elastic search. Port 9200 is usually the default http port and 9300 is the default transport port. In put elastic search we need to use the transport port. 2. If the port is correct try to issue a PUT (https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html) call to elastic search using the json you generated and see if that goes through. -- Arpit On Apr 6, 2016, at 9:41 AM, philippe.gib...@orange.com<mailto:philippe.gib...@orange.com> wrote: Hello My context nifi 0.6.0 on Ubuntu 14.0 my small use case is : ‘sending JSON notifications arriving on http to an ElasticSearch instance ‘ So I started to develop a DataFlow with 1 handleHttprequest sending in parallel to 2 processors -to a Putfile ( perfect I see the JSON notifs on my File System ) - to a PutElasticSearch ( correctly configured with index, type and uuid but it does not work) Elastic Search on the linux console says : java.lang.IllegalArgumentException: empty text and if I look to stats/provenance in the PutElasticSearch processor the data is there … but not sent to ElasticSearch on localhost:9200 Any help would be nice ( perhaps some processor is mandatory before ElasticSearch in the chain ? in my DF just the handleHttprequest processor is preceding the ElasticSearch one ) Thx Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
