And I also do something after commit and rollback:
Commit --OnComponentOK--> tWarn_1
Rollback --OnComponentOK--> tWarn_2
Here is what I put in the "Warn message" area:
tWarn_1:
String.format("%s: %s", context.uac_Schema+"."+ context.tgtTable,"Num of New jobs inserted = "+((Integer)globalMap.get("tDBOutput_2_NB_LINE_INSERTED"))+" & "+"Num of jobs updated = "+((Integer)globalMap.get("tDBOutput_1_NB_LINE_UPDATED")))
The tWarn_1 is very nice: it prints out how many rows the job inserted/updated/deleted depending on the job designs. It is very useful during the testing/troubleshooting when job fails.
But I have never seen tWarn_2 print anything for me so far even though sometimes my job failed --
and my question: is the tWarn_2 unnecessary component here? Could anyone provide a simple example of using tOracleRollback and print out the rollback error message for me ( and others like me who may have the same confusion)?
Rollback components are used to make sure that entire data is rolled back in case the input data volume is high and your DB load failed in between.
For example, you have 1 million records and data will be written to table at regular intervals since we will not be able to pump 1 million in a single batch. When the data load reached 50,000 records, you got some error data and job failed. Now, the initial 50k records are still in DB but ideally you need to roll these data back. tDBRollback helps in this context where it will rollback from all the associated tables (this table and any previous tables) which got loaded under same tDBConnection unless you have given an explicit commit.
Could you please refer the link below for a quick sample scenario too?
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved
