[ https://issues.apache.org/jira/browse/CALCITE-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670624#comment-16670624 ]
Julian Hyde commented on CALCITE-2065: -------------------------------------- Yes. We should be forgiving about the case of URL parameters. I feel strongly that the property should be called "autoCommit" (to match \{{java.sql.Connection.setAutoCommit(boolean)}}) but we should accept both 'autocommit=true' and 'autoCommit=false' in the URL. > Make “autoCommit” an accepted parameter in the JDBC URL > ------------------------------------------------------- > > Key: CALCITE-2065 > URL: https://issues.apache.org/jira/browse/CALCITE-2065 > Project: Calcite > Issue Type: Improvement > Components: avatica > Reporter: Christian Tzolov > Assignee: Josh Elser > Priority: Major > > At the moment there is no declarative way to set connection's "autoCommit" > property. It defaults to `false`. > There are couple of use cases (like apache zeppelin integration) where the > ability to set the autocommit property to true are required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)