[
https://issues.apache.org/jira/browse/HIVE-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247876#comment-14247876
]
Lefty Leverenz commented on HIVE-4812:
--------------------------------------
bq. "I don't think this has to even be documented for users, but might be
useful to developers."
Perhaps EXPLAIN LOGICAL should be documented, even if it's only useful for
developers.
* [EXPLAIN Syntax |
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Explain#LanguageManualExplain-EXPLAINSyntax]
> Logical explain plan
> --------------------
>
> Key: HIVE-4812
> URL: https://issues.apache.org/jira/browse/HIVE-4812
> Project: Hive
> Issue Type: Bug
> Components: Diagnosability
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> Fix For: 0.12.0
>
> Attachments: HIVE-4812.1.patch, HIVE-4812.2.patch, HIVE-4812.3.patch
>
>
> In various situations it would have been useful to me to glance at the
> operator plan before we break it into tasks and apply join, total order sort,
> etc optimizations.
> I've added this as an options to explain. "Explain logical <QUERY>" will
> output the full operator tree (not the stage plans, tasks, AST etc).
> Again, I don't think this has to even be documented for users, but might be
> useful to developers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
