Hi Luis, thanks for the hint... this is indeed a good work around. So simple that I should have thought about it 😉
Regards ________________________________ From: Luis Carmona <[email protected]> Sent: Monday, February 4, 2019 4:23 PM To: users Subject: Re: PutElasticsearchHttp can not use Flowfile attribute for ES_URL HI Jean, I'm not even near to be an expert on NIFI, but I did accomplish to put to work an scenario similar to the one you describe. I was able to read some data, process it and store the Json payload in ES. I used HTTP invoke, instead of ES Processors. Hope it helps you. Regards, LC ________________________________ De: "Jean-Sebastien Vachon" <[email protected]> Para: "users" <[email protected]> Enviados: Lunes, 4 de Febrero 2019 18:16:23 Asunto: PutElasticsearchHttp can not use Flowfile attribute for ES_URL Hi all, I was just finishing modifying my flow to make it more reusable by having my source document containing information about where to store the final document (some Elasticsearch index) Everything was fine until I found out that the PutElasticsearchHttp's documentation was saying this... Supports Expression Language: true (will be evaluated using variable registry only) It looks like this restriction appeared around Nifi 1.6 (as per the documentation)... is there a reason for such a limitation? My current flow was extracting the information from the input JSON document and saving the information inside a Flow attribute. What can I do about this? I don't like monkey patching.. is there any other way to get around this? Thanks
