Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 01-15-2019 04:47 PM
Hi Team,
Please help me on the below issue
I am ingesting the Data From Oracle to PostgresSql Using NiFi.
We have huge data and continuously generating from sources, I want to update attributes and delete attributes using NiFi
My Flow is: QueryDatabaseRecord-->UpdateAttribute-->PutDatabaseRecord
Appreciate your help.
Thank you,
Created 01-16-2019 12:18 AM
If you are able to identify insert/updates then set statement.type attribute to the flowfile then based on the attribute value PutDatabaseRecord processor will run Update/Insert/Delete Statements.
-
This is kind of hacky way to do this:
If you are not able to identify inserts/updates then split the records into each record individually using SplitRecord processor then run two/three successive PutDatabaseRecord processors.
Flow:
1. FirstPutDatabaseRecord //insert statementtype use failure connection to next PutDatabaseRecord 2.SecondPutDatabaseRecord //update statementtype,use failure connection to next PutDatabaseRecord. 3.ThirdPutDatabaseRecord //delete statementtype
Note: I'm guessing this flow but rearrange these processors as per your logic.
Created 01-16-2019 12:18 AM
If you are able to identify insert/updates then set statement.type attribute to the flowfile then based on the attribute value PutDatabaseRecord processor will run Update/Insert/Delete Statements.
-
This is kind of hacky way to do this:
If you are not able to identify inserts/updates then split the records into each record individually using SplitRecord processor then run two/three successive PutDatabaseRecord processors.
Flow:
1. FirstPutDatabaseRecord //insert statementtype use failure connection to next PutDatabaseRecord 2.SecondPutDatabaseRecord //update statementtype,use failure connection to next PutDatabaseRecord. 3.ThirdPutDatabaseRecord //delete statementtype
Note: I'm guessing this flow but rearrange these processors as per your logic.
Created 02-12-2021 12:10 AM
This solution will not work. The failure flow does not go to next putDatabaseRecord processor because the error is exception. Failure flow files will go nowhere