Good morning @cotopaul @SAMSAL First of all thank you very much for your time Ok Ok so I see that I missunderstood how QueryDatabaseTable is "triggered". @SAMSAL I knew about those configuration but as I said I thought this processor only do the query when a new record is inserted in the database taking reference the maximum column value. Makes sense now the postgresql log...the querys executed every second since my RunSchedule is on default (0).  What I use minifi for is to load sales from a supermarket then send it via API (and others transformations), so I need this to be in real time as soon as the client paid. I guess I have to define Run Schedule every few seconds. @cotopaul I will take a look at my DBCPConnectionPool, this info it´s helpfull Thank you all.  ... View more

Hi @MWM ,   What you are describing is a classical data enrichment pattern that can be achieved using ForkEnrichment & JoinEnrichment processors. For more information on this please refer to : https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.20.0/org.apache.nifi.processors.standard.JoinEnrichment/additionalDetails.html   Based on your scenario the "SQL" strategy of the JoinEnrichment will work the best for you since you can select the main fields (system, name, surname, phone, mail) from the original flowfile data and select proffesion and department from enrichment result:   SELECT o.system, o.name, e.surname,o.phone, o.mail, e.profession, e.department FROM original o LEFT OUTER JOIN enrichment e ON o.name= e.name Since you are splitting the CSV and enrich per record then you can just join by name. If you have an API where you can get a collection of user information then you dont have to split and you can do the enrichment on multiple records from the CSV vs. returned records from the API json output , however be aware that if you have large data set this strategy "... can lead to heap exhaustion and cause stability problems or OutOfMemoryErrors to occur". Please review the link above to see how this can be mitigated.   If you find this is helpful please accept solution. Thanks     ... View more

I see, it work! Thanks for your information ... View more

Thanks @SAMSAL  it worked for me... ... View more

@SAMSAL This looks like a plausible solution. Let me try it out.  ... View more

@Diga  In a scenario like this, the first thing to ask yourself is "How would I do this outside of NiFi?".  If you were to use curl from command line, how would you handle authentication with the Polarion ALM rest-api endpoints?  The answer there would help with how you would handle it within NiFi and assist in getting a better response in the community.  @SAMSAL provided some great suggestions of possible methods. Matt ... View more

thank you so much! i'm moving forward again! ... View more

Hi @CommanderLaus , If you do anything manually with the processor you are trying to change its Running State through the API, then yes the revision will be updated. In my case what I do is basically the first API InvokeHttp is to get the latest revision using the following GET API:   https://localhost:8443/nifi-api/processors/${pipeline.start.processor.id}   This will give the following response where you can parse the latest "version" value using something like EvaluateJsonPath processor and store the value in an attribute:   { "revision": { "clientId": "value", "version": 0, "lastModifier": "value" }, "id": "value", "uri": "value", "position": {…}, "permissions": {…}, "bulletins": [{…}], "disconnectedNodeAcknowledged": true, "component": {…}, "inputRequirement": "value", "status": {…}, "operatePermissions": {…} }   Then use extracted version attribute to build the next API post Body , for example in my case I use ReplaceText processor to generate the post body :   { "revision": { "clientId": "${pipeline.start.processor.id}", "version": ${processorVersion} }, "state": "...", "disconnectedNodeAcknowledged": true }   Hope that helps.       ... View more

Thanks @SAMSAL  for recommending @MattWho  ... View more