[
https://issues.apache.org/jira/browse/HIVE-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432018#comment-15432018
]
Gopal V edited comment on HIVE-14362 at 8/23/16 2:50 AM:
---------------------------------------------------------
The local path was traced down to -
config.setExplainRootPath(ctx.getLocalTmpPath()); in SemanticAnalyzer.
The path for collecting stats has to be in the Hive Session dir on HDFS, I'll
try to patch this tomorrow and try running again.
(btw, this impl has something amazing in it - it gives me counters even if I
kill a query)
was (Author: gopalv):
The local path was traced down to -
config.setExplainRootPath(ctx.getLocalTmpPath()); in SemanticAnalyzer.
The path for collecting stats has to be in the Hive Session dir on HDFS, I'll
try to patch this tomorrow and try running again.
> 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,
> 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)
