[jira] [Resolved] (NIFI-12010) Handle auto-commit and commit based on driver capabilities in SQL components

["Matt Burgess (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-12010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess resolved NIFI-12010.
---------------------------------
    Fix Version/s: 2.0.0
                   1.24.0
                       (was: 1.latest)
                       (was: 2.latest)
       Resolution: Fixed

> 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: 2.0.0, 1.24.0
>
>          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)