[ 
https://issues.apache.org/jira/browse/HIVE-15060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15617281#comment-15617281
 ] 

Hive QA commented on HIVE-15060:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835878/HIVE-15060.2.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 10628 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_5] 
(batchId=90)
org.apache.hive.spark.client.TestSparkClient.testJobSubmission (batchId=272)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1874/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1874/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-1874/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12835878 - PreCommit-HIVE-Build

> Remove the autoCommit warning from beeline
> ------------------------------------------
>
>                 Key: HIVE-15060
>                 URL: https://issues.apache.org/jira/browse/HIVE-15060
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Tao Li
>            Assignee: Tao Li
>         Attachments: HIVE-15060.1.patch, HIVE-15060.2.patch
>
>
> WARN jdbc.HiveConnection: Request to set autoCommit to false; Hive does not 
> support autoCommit=false.
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> 0: jdbc:hive2://ctr-e89-1466633100028-0275-01
> By default, this beeline setting is false, while hive only support 
> autoCommit=true for now. So this warning does mot make sense and should be 
> removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to