[ https://issues.apache.org/jira/browse/HIVE-11293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981485#comment-14981485 ]
Alan Gates commented on HIVE-11293: ----------------------------------- The spec doesn't seem to specify what to do if someone calls setAutoCommit(false) and the engine doesn't support multi-statements transactions. But it seems to me we should at least issue a warning in the logs and in the SQLWarnings. > HiveConnection.setAutoCommit(true) throws exception > --------------------------------------------------- > > Key: HIVE-11293 > URL: https://issues.apache.org/jira/browse/HIVE-11293 > Project: Hive > Issue Type: Bug > Components: JDBC > Reporter: Andriy Shumylo > Assignee: Michał Węgrzyn > Priority: Minor > Attachments: HIVE-11293.patch > > > Effectively autoCommit is always true for HiveConnection, however > setAutoCommit(true) throws exception, causing problems in existing JDBC code. > Should be > {code} > @Override > public void setAutoCommit(boolean autoCommit) throws SQLException { > if (!autoCommit) { > throw new SQLException("disabling autocommit is not supported"); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)