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]>) 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]> 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. >> >
