[
https://issues.apache.org/jira/browse/HIVE-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679477#comment-14679477
]
Hive QA commented on HIVE-11501:
--------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12749413/HIVE-11501.patch
{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 9344 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.hbase.TestPigHBaseStorageHandler.org.apache.hive.hcatalog.hbase.TestPigHBaseStorageHandler
org.apache.hive.jdbc.TestSSL.testSSLFetchHttp
org.apache.hive.spark.client.TestSparkClient.testSyncRpc
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4895/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/4895/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-4895/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 3 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12749413 - PreCommit-HIVE-TRUNK-Build
> 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)
