[
https://issues.apache.org/jira/browse/HIVE-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419249#comment-15419249
]
Gopal V edited comment on HIVE-14362 at 8/12/16 6:25 PM:
---------------------------------------------------------
[~pxiong]: the branch + counter to profile was abandoned earlier due to known
performance issues.
https://issues.apache.org/jira/browse/HIVE-4318?focusedCommentId=13629957&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13629957
The crucial test is how much this extra code impacts perf when it is disabled.
was (Author: gopalv):
[~pxiong]: this approach was abandoned earlier due to known performance issues
-
https://issues.apache.org/jira/browse/HIVE-4318?focusedCommentId=13629957&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13629957
> 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
>
>
> 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)
