[
https://issues.apache.org/jira/browse/NIFI-12010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763896#comment-17763896
]
ASF subversion and git services commented on NIFI-12010:
--------------------------------------------------------
Commit af8128bb5c26e418d31ec38741648dd87607c33b in nifi's branch
refs/heads/support/nifi-1.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=af8128bb5c ]
NIFI-12010: Handle auto-commit and commit based on driver capabilities in SQL
components
Signed-off-by: Arpad Boda <[email protected]>
This closes #7663
> Handle auto-commit and commit based on driver capabilities in SQL components
> ----------------------------------------------------------------------------
>
> Key: NIFI-12010
> URL: https://issues.apache.org/jira/browse/NIFI-12010
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some JDBC drivers throw an exception when calling setAutoCommit(false), even
> if the auto-commit setting for the driver is already false. Although
> unfortunate, I'm not sure it is a violation of the JDBC API. The SQL
> components in NiFi that use the JDBC API should catch
> SQLFeatureNotSupportedException and perhaps log a debug message but otherwise
> proceed.
> Same goes for connection.commit() and connection.rollback(), these should not
> be explicitly called if auto-commit is true for the connection.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
