[
https://issues.apache.org/jira/browse/HIVE-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083060#comment-17083060
]
Zoltan Haindrich commented on HIVE-23189:
-----------------------------------------
so you suggests everyone should write "EXPLAIN PROFILE select 1" from now on -
I think almost every database system uses the keywords "explain analyze" for
these kind of output - why should Hive be different?
I strongly disagree with this change.
I leave a veto vote here to declare that acceptance of this change should be
moved into a "Lazy majority" before it could be accepted
https://cwiki.apache.org/confluence/display/Hive/Bylaws
-1
> Change Explain ANALYZE to Explain PROFILE
> -----------------------------------------
>
> Key: HIVE-23189
> URL: https://issues.apache.org/jira/browse/HIVE-23189
> Project: Hive
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
> Attachments: HIVE-23189.1.patch
>
>
> {code:none}
> EXPLAIN
> [EXTENDED|CBO|AST|DEPENDENCY|AUTHORIZATION|LOCKS|VECTORIZATION|ANALYZE] query
> {code}
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Explain#LanguageManualExplain-TheANALYZEClause
> In Hive, there is an {{EXPLAIN ANALYZE}} query. This can get a bit confusing
> because you can run an {{EXPLAIN ANALYZE}} against an {{ANALYZE TABLE}}
> statement, so you have something like,...
> {code:sql}
> EXPLAIN ANALYZE ANALYZE TABLE `myTable` COMPUTE STATISTICS;
> {code}
> I would like to propose that the name be changed to {{EXPLAIN PROFILE}}.
> This borrows from Apache Impala because it has a {{PROFILE}} command which
> produces the stats that actually occurred during the query run (much like
> this Hive feature).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
