[HIVE-11501] HiveConnection.readOnly always throws a "Method not supported" exception

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Assignee: Michał Węgrzyn
• Reporter: Michał Węgrzyn
• Created: 08/Aug/15 08:25
• Updated: 16/Feb/16 23:52
• Resolved: 24/Aug/15 05:16

Description

HiveConnection.setReadOnly's automatically generated implementation always throws a generic "Method not supported" exception and thus is not compliant with the JDBC spec. Per JDBC spec, an exception can be thrown only if the connection is closed, DB access error occurs or the method is called during a transaction (which is not a case for HiveConnection).

JDBC spec does not say a word about not supporting the method by the driver. The most correct behavior could be to throw only if the request tries to enable the read-only mode (as HiveConnection.isReadOnly always returns false).

This issue is a blocker for JDBC connection pools (i.e. HikariCP) that expect JDBC-compliant behavior from the driver.