Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
None
-
None
-
None
Description
For PutSQL processor,if the 'Support Fragmented Transactions' is true, the processor will process all FlowFiles with that fragment.identifier as a single transaction;
In actuality,it works.
But when some sql of the transaction failed and <Rollback On Failure> is false , the database transaction will not roll back.
Sometimes,we need the database transaction rollback and do not want the flowfile rollback, we need that the failed database transaction route to REL_FAILURE.
If the <Support Fragmented Transactions>is true and <Rollback On Failure> is false , I think it should still support the capability of database transaction rollback, for example :it should add a property (like <Support Fragmented Transactions RollBack>) which can indicate that whether the processor support database transaction rollback when the 'Support Fragmented Transactions' is true .Of course ,when <ROLLBACK_ON_FAILURE> is true ,<Support Fragmented Transactions RollBack> will be ignored
Attachments
Issue Links
- links to