Can you elaborate more on what you are trying to split? The transactions in the first and second split you specified seem to be identical. ... View more

Hi,   You can try the following spec:   [ { "operation": "shift", "spec": { "*": "&", "responseData": { "responseList": { "*": { "individualInfo": { "#${UUID()}": "responseData.responseList.[&2].individualInfo.activityUID", "firstName": "responseData.responseList.[&2].individualInfo.&", "middleName": "responseData.responseList.[&2].individualInfo.&", "lastName": "responseData.responseList.[&2].individualInfo.&", "dateOfBirth": "responseData.responseList.[&2].individualInfo.&" } } } } } } ]   If that helps please accept solution. Thanks ... 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

Hi @Anderosn, Similar question was asked before, see if the following posts can help: https://community.cloudera.com/t5/Support-Questions/How-to-load-json-record-to-postgres-as-json-datatype/m-p/345779#M234644 https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Insert-json-data-into-table-as-single-column/m-p/363974 https://community.cloudera.com/t5/Support-Questions/nifi-Writing-Inserting-entire-flowfile-content/td-p/205367   If Any of the links work for your case please accept solution. Thanks ... View more

Hi @brajeshreddy , I dont think you can achieve this using the ControlRate processor. Instead I recommend the solution mentioned here: https://stackoverflow.com/questions/69893107/nifi-activate-a-flow-file-after-a-previous-flow-file-goes-through-the-downstre   If you have a cluster then make sure that the top processor is executing on the Primary node.   hope that helps. Thanks   ... View more

Hi @Diga , Here are some videos to help you get started with the InvokeHttp Processor: https://www.youtube.com/watch?v=aNrdWYy4i34 https://www.youtube.com/watch?v=SZhX_gce63E https://www.youtube.com/watch?v=Jk7H8w3evN0   As far as logging in and authentication, it depends what kind of authentication the Rest API has. If it has simple authentication (username & password) you can enter those in the Basic Authentication Username & Basic Authentication Password properties. If you need to get Access Token (OAuth2) then you either obtain this through another InvokeHttp processor and pass it to the actual rest api invokehttp as "Authorization" header property (dynamically added to the processor), or second option is to take advantage of the "OAuth2 Access Token provider" in the InvokeHttp processor by setting up "StandardOauth2AccessTokenProvider" service and provide the credentials  and the access token url there.   Hope that helps. Thanks   ... View more