hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (JIRA)" <>
Subject [jira] [Commented] (HIVE-948) more query plan optimization rules
Date Fri, 15 Feb 2013 03:11:13 GMT


Phabricator commented on HIVE-948:

navis has commented on the revision "HIVE-948 [jira] more query plan optimization rules".

  ql/src/java/org/apache/hadoop/hive/ql/ppd/ I don't know
well about the issue, but there is still a rule(R7:MAPJOIN%) about mapjoin in genMapRedTasks()
method in SemanticAnalyzer. what's that?

  I'll remove that.
  ql/src/java/org/apache/hadoop/hive/ql/optimizer/ ok, NonBlockingOpDeDupProc
will be good. When we need some other cleaning ups, we can rename it or do other things.




To: JIRA, ashutoshc, navis

> more query plan optimization rules 
> -----------------------------------
>                 Key: HIVE-948
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Ning Zhang
>            Assignee: Navis
>         Attachments: HIVE-948.D8463.1.patch, HIVE-948.D8463.2.patch
> Many query plans are not optimal in that they contain redundant operators. Some examples
are unnecessary select operators (select followed by select, select output being the same
as input etc.). Even though these operators are not very expensive, they could account for
around 10% of CPU time in some simple queries. It seems they are low-hanging fruits that we
should pick first. 
> BTW, it seems these optimization rules should be added at the last stage of the physical
optimization phase since some redundant operators are added to facilitate physical plan generation.

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:

View raw message