[
https://issues.apache.org/jira/browse/DRILL-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494561#comment-14494561
]
Parth Chandra commented on DRILL-2782:
--------------------------------------
My suggestion would be to return TRANSACTION_NONE in
getTransactionIsolationLevel and in commit/rollback follow the semantics of
setAutoCommit(true) and throw a SQLException.
> Decide, implement behavior for transaction-related JDBC methods
> ---------------------------------------------------------------
>
> Key: DRILL-2782
> URL: https://issues.apache.org/jira/browse/DRILL-2782
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Daniel Barclay (Drill)
>
> Officially, JDBC requires transaction support. Because of that, the JDBC
> specification (PDF document and Javadoc) addresses the behavior of
> transaction-related methods only for the case in which transactions are
> supported.
> In particular, JDBC does not specify the behavior when transactions are not
> supported.
> Therefore, it is not clear what behavior a JDBC client tool would expect, or
> be programmed to handle, from a JDBC driver and back end that do not support
> transactions (that is, Drill).
> In turn, that means that it is not clear exactly what Drill's JDBC driver's
> transaction-related methods should do. ,
> [IN PROGRESS--Why the heck does Jira intercept some magic keystroke and
> submit things without confirmation?!]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
