hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namit Jain (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1750) Remove Partition Filtering Conditions when Possible
Date Tue, 02 Nov 2010 06:01:26 GMT

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

Namit Jain commented on HIVE-1750:
----------------------------------

OpProcFactory:

      for (Partition p: prunedPartList.getConfirmedPartns()) {
        if (!p.getTable().isPartitioned()) {
          return null;
        }
      }
      for (Partition p: prunedPartList.getUnknownPartns()) {
        if (!p.getTable().isPartitioned()) {
          return null;
        }
      }

Why are the above changes needed ?


The overall approach looks good - still looking in detail.



> Remove Partition Filtering Conditions when Possible
> ---------------------------------------------------
>
>                 Key: HIVE-1750
>                 URL: https://issues.apache.org/jira/browse/HIVE-1750
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Siying Dong
>            Assignee: Siying Dong
>         Attachments: HIVE-1750.1.patch, HIVE-1750.2.patch
>
>
> For some simple queries, partition filtering constraints take 8% of CPU time (now 16%
since we filter twice) even if the result is always true. When possible, we should remove
these constraints to save CPU times.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message