[
https://issues.apache.org/jira/browse/HIVE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680534#comment-14680534
]
Sergey Shelukhin commented on HIVE-11501:
-----------------------------------------
+1
> HiveConnection.readOnly always throws a "Method not supported" exception
> ------------------------------------------------------------------------
>
> Key: HIVE-11501
> URL: https://issues.apache.org/jira/browse/HIVE-11501
> Project: Hive
> Issue Type: Bug
> Reporter: Michał Węgrzyn
> Assignee: Michał Węgrzyn
> Attachments: HIVE-11501.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
