[
https://issues.apache.org/jira/browse/HIVE-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384732#comment-14384732
]
Hive QA commented on HIVE-9780:
-------------------------------
{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/12707691/HIVE-9780.05.patch
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 8680 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver_explainuser_1
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_schemeAuthority
org.apache.hadoop.hive.thrift.TestHadoop20SAuthBridge.testMetastoreProxyUser
org.apache.hadoop.hive.thrift.TestHadoop20SAuthBridge.testSaslWithHiveMetaStore
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3185/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/3185/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-3185/
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: 4 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12707691 - PreCommit-HIVE-TRUNK-Build
> Add another level of explain for RDBMS audience
> -----------------------------------------------
>
> Key: HIVE-9780
> URL: https://issues.apache.org/jira/browse/HIVE-9780
> Project: Hive
> Issue Type: Improvement
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Priority: Minor
> Attachments: HIVE-9780.01.patch, HIVE-9780.02.patch,
> HIVE-9780.03.patch, HIVE-9780.04.patch, HIVE-9780.05.patch
>
>
> Current Hive Explain (default) is targeted at MR Audience. We need a new
> level of explain plan to be targeted at RDBMS audience. The explain requires
> these:
> 1) The focus needs to be on what part of the query is being executed rather
> than internals of the engines
> 2) There needs to be a clearly readable tree of operations
> 3) Examples - Table scan should mention the table being scanned, the Sarg,
> the size of table and expected cardinality after the Sarg'ed read. The join
> should mention the table being joined with and the join condition. The
> aggregate should mention the columns in the group-by.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
