Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
git.commit.id.abbrev=e92db23
Currently drill throws an UnsupportedOperationException when we call "commit" on the Connection object.
I am not exactly sure what "commit" should do in the context of drill. But at the very least doing nothing is better than throwing the above exception since a few analytic tools might be using this method.
Below is the documentation from the JDBC spec :
void commit() throws SQLException - Makes all changes made since the previous commit/rollback permanent and releases any database locks currently held by this Connection object. This method should be used only when auto-commit mode has been disabled. Throws: SQLException - if a database access error occurs, this method is called while participating in a distributed transaction, if this method is called on a closed connection or this Connection object is in auto-commit mode
Attachments
Issue Links
- is superceded by
-
DRILL-2782 Decide, implement behavior for transaction-related JDBC methods
- Resolved
- relates to
-
DRILL-2445 JDBC : Connection.rollback method currently throws UnsuportedOperationException
- Resolved
-
DRILL-2769 many(?) JDBC methods throw non-SQLException exceptions (e.g., UnsupportedOperationException, RuntimeException)
- Resolved