[
https://issues.apache.org/jira/browse/HIVE-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450022#comment-15450022
]
Hive QA commented on HIVE-14362:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12826218/HIVE-14362.06.patch
{color:green}SUCCESS:{color} +1 due to 7 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 5 failed/errored test(s), 10472 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.org.apache.hadoop.hive.cli.TestCliDriver
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[vector_join_part_col_char]
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_3]
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainuser_3]
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/1044/testReport
Console output:
https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/1044/console
Test logs:
http://ec2-204-236-174-241.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-MASTER-Build-1044/
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: 5 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12826218 - PreCommit-HIVE-MASTER-Build
> Support explain analyze in Hive
> -------------------------------
>
> Key: HIVE-14362
> URL: https://issues.apache.org/jira/browse/HIVE-14362
> Project: Hive
> Issue Type: New Feature
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Attachments: HIVE-14362.01.patch, HIVE-14362.02.patch,
> HIVE-14362.03.patch, HIVE-14362.05.patch, HIVE-14362.06.patch,
> compare_on_cluster.pdf
>
>
> Right now all the explain levels only support stats before query runs. We
> would like to have an explain analyze similar to Postgres for real stats
> after query runs. This will help to identify the major gap between
> estimated/real stats and make not only query optimization better but also
> query performance debugging easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)