hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-17683) Add explain locks <sql> command
Date Sun, 29 Jul 2018 18:02:00 GMT


Hive QA commented on HIVE-17683:

Here are the results of testing the latest attachment:

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

{color:red}ERROR:{color} -1 due to 13 failed/errored test(s), 14413 tests executed
*Failed tests:*
TestBeeLineDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=258)
TestDummy - did not produce a TEST-*.xml file (likely timed out) (batchId=258)
TestMiniDruidCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=258)
TestMiniDruidKafkaCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=258)
TestTezPerfCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=258)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[mm_all] (batchId=70)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[mm_all] (batchId=153)
org.apache.hadoop.hive.ql.TestWarehouseExternalDir.testManagedPaths (batchId=235)
org.apache.hive.service.TestHS2ImpersonationWithRemoteMS.testImpersonation (batchId=243)
org.apache.hive.spark.client.rpc.TestRpc.testServerPort (batchId=310)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 13 tests failed

This message is automatically generated.

ATTACHMENT ID: 12933520 - PreCommit-HIVE-Build

> Add explain locks <sql> command
> -------------------------------
>                 Key: HIVE-17683
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Igor Kryvenko
>            Priority: Critical
>         Attachments: HIVE-17683-branch-3.0.patch, HIVE-17683-branch-3.patch, HIVE-17683.01.patch,
HIVE-17683.02.patch, HIVE-17683.03.patch, HIVE-17683.04.patch, HIVE-17683.05.patch, HIVE-17683.06.patch
> Explore if it's possible to add info about what locks will be asked for to the query
> Lock acquisition (for Acid Lock Manager) is done in DbTxnManager.acquireLocks() which
is called once the query starts running.  Would need to refactor that.

This message was sent by Atlassian JIRA

View raw message