[
https://issues.apache.org/jira/browse/HIVE-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gunther Hagleitner updated HIVE-4812:
-------------------------------------
Description:
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.
was:
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 physical <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.
> Logical explain plan
> --------------------
>
> Key: HIVE-4812
> URL: https://issues.apache.org/jira/browse/HIVE-4812
> Project: Hive
> Issue Type: Bug
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
