hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <>
Subject [jira] Commented: (HIVE-578) Refactor partition pruning code as an optimizer transformation
Date Wed, 15 Jul 2009 17:15:14 GMT


Ashish Thusoo commented on HIVE-578:

yes that makes sense. In fact that needs to be done to make pruning work with select * from
T where T.part = xyz kind of queries and I ran into that a few days back. I have punted that
for the first stage and still rely on the old pruning stuff for such queries and when predicate
pushdown is switched off. I have it mostly passing the tests except for sampling tests where
in the predicate pushdown code seems not to be merging the two filter operators and I have
made that assumption in my code. Will update today with the version sans the new tests and
some cleanup. That way we can see how sampling stuff can work with this as well.

> Refactor partition pruning code as an optimizer transformation
> --------------------------------------------------------------
>                 Key: HIVE-578
>                 URL:
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.3.0
>            Reporter: Ashish Thusoo
>            Assignee: Ashish Thusoo
>         Attachments: patch-578.txt
> Some bugs with partition pruning have been reported and the correct fix for many of them
is to rewrite the partition pruning code as an optimizer transformation which gets kicked
in after the predicate pushdown code. This refactor also uses the graph walker framework so
that the partition pruning code gets consolidated well with the frameworks and does not work
on the query block but rather works on the operator tree.

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

View raw message