Member since
08-24-2022
3
Posts
0
Kudos Received
0
Solutions
12-03-2024
06:01 AM
2 Kudos
Hi @SS_Jin , Glad to hear that my post helped. Its really hard to suggest something specially when I dont have all the details of what you are trying to do but from what I read, I think Join\Fork Enrichment would work better in these scenarios. The mergerecord way could be problematic when you are reading multiple sources and multiple CSVs where merge behavior can be unpredictable. Also depending on what type of enrichment you are trying to do and how complex its but if you have one to one mapping between record in the DB vs CSV and you are trying to override some data or add new one then you might also consider the LookupRecord processor to simplify your data flow where you dont have to use branching to read and then merge the different sources which might endup saving you some overhead. https://community.cloudera.com/t5/Community-Articles/Data-flow-enrichment-with-NiFi-part-1-LookupRecord-processor/ta-p/246940
... View more
05-26-2023
07:38 AM
1 Kudo
Hi, The request Body has to be provided as flowfile to the InvokeHttp Processor per the processor description: You can use an upstream processor to the InvokeHttp like ReplaceText processor to generate the request body a follows: To send incoming flowfile content as Request Body , make sure the following property of the invokehttp processor is set to true (default): To make sure you are always getting a response no matter if its successful or not make sure to set the following invokehttp processor to true (default false): If that helps please accept solution. Thanks
... View more
08-24-2022
11:26 AM
@skoch244 You should refer the following community article where we have explained updating/resetting offset possibilities for the topic in the Nifi processor. https://community.cloudera.com/t5/Support-Questions/Offset-handling-in-Apache-NiFi-consumeKafka/m-p/303112/highlight/true#M221400 Please let us know if this information helped you. Thank you.
... View more