hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4812) Explain plan for physical operators
Date Thu, 04 Jul 2013 00:35:20 GMT

    [ https://issues.apache.org/jira/browse/HIVE-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699637#comment-13699637
] 

Navis commented on HIVE-4812:
-----------------------------

Hive uses term 'Logical Optimizer' which modifies operator tree and 'Physical Optimizer' which
modifies tasks. I'm a little worry about more confusion would be introduced by new term 'physical
operators'.
                
> 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, HIVE-4812.2.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

Mime
View raw message