Another option that may work better for this use case is the LookupAttribute processor. This can be used in conjunction with the rest lookup service (the term REST here is a misnomer. It’s an http based lookup service and not tied to REST) to hit an HTTP endpoint and then the result can be added as an attribute, I believe. It’s been a while since I looked at the processor and rest lookup service but I think it will provide what you need.
Thanks -Mark Sent from my iPhone On Jan 27, 2020, at 6:18 PM, Etienne Jouvin <[email protected]> wrote: With Notify, you can specify attributs to copy from thé Notify to the wait. At very first, that what I used. But you have a "latency" between thé two process, because of thread and I prefer to use distribute cache. But careful also, the distribute cache Can ne access from other point... Le lun. 27 janv. 2020 à 20:45, Contacto Control Cobros <[email protected]<mailto:[email protected]>> a écrit : Thanks Etienne for your response, I tried both approaches. The second goes better with what I need, because I require the sessionID and with the first approach I didn't find how to share the sessionID after the Notify. I just hope that storing the content in the distributed cache is better than having it as an attribute. El lun., 27 ene. 2020 a las 11:14, Etienne Jouvin (<[email protected]<mailto:[email protected]>>) escribió: Hello. I manage to do this in two ways : 1. Use Wait / Notify process. Put the original content in the wait, and after your post is finished call the Notify to free the original one. 2. Or use a distribute cache map. Store the original content in the cache, do your stuff and then request the original content from the cache. Hope it helps Le lun. 27 janv. 2020 à 17:12, Contacto Control Cobros <[email protected]<mailto:[email protected]>> a écrit : Hello community I need to read a JSON file that is obtained as an attachment to an email with a specific subject, so far there is no problem. Then I need to make a POST to get a sessionID, with username and password that I have as a parameter. Finally I need to send the JSON content using another POST request, sending as header the sessionID that I obtained. My problem is how to make an InvokeHTTP (POST), without losing the content I read in the first step. Nifi always requires that the body for the POST be the Flowfile content. I would not like to load the JSON as an attribute, it can be very large. I appreciate your help.
