[ https://issues.apache.org/jira/browse/NIFI-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ZhangCheng closed NIFI-7140. ---------------------------- > PutSql support database transaction rollback when <ROLLBACK_ON_FAILURE >is > false > -------------------------------------------------------------------------------- > > Key: NIFI-7140 > URL: https://issues.apache.org/jira/browse/NIFI-7140 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Affects Versions: 1.11.1 > Reporter: ZhangCheng > Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)