[
https://issues.apache.org/jira/browse/HIVE-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698624#comment-13698624
]
Gunther Hagleitner commented on HIVE-4812:
------------------------------------------
I was going back and forth on this. I don't think it's that clear cut. The plan
consists entirely of physical operators and can contain stuff like mapjoin if
you're using hints. Not something I'd expect from a logical plan. Reduce sinks
also don't easily map to algebraic operations. On the other hand you can't run
the plan on MR as it stands.
I think the name "physical" is appropriate, and I tend to use MR plan for the
task plan. But if you feel strongly, I'd be happy to change to logical, or
maybe something else - less specific (explain operators <QUERY>?)
Thoughts?
> Explain plan for physical operators
> -----------------------------------
>
> 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
>
>
> 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.
--
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
