Grokbase Groups Pig dev March 2013

On March 20, 2013, 12:42 a.m., Dmitriy Ryaboy wrote:, line 224

(A and B) or (C and D)

is impossible if (A or C) is false. We can push this up, while retaining the original filter to apply the original filter.
Rohini Palaniswamy wrote:
So just to confirm, you want to extract A and C from each AND condition and push (A OR C) as the partition filter for optimization and still leave ((A AND B) or (C AND D)) to be applied on each tuple?
correct, unless my logic is wrong.

I actually think we made a bad decision when we decided that if we can push partitions down, we can drop the filter on the pig side -- this means we can't take advantage of partial filters loaders might support (for example, a bloom filter a loader can consult to return just the rows that "probably" match the condition, as opposed to definitely match. With filter removal, we have to have loaders implement a second-pass filtering on top of such filters).

- Dmitriy

This is an automatically generated e-mail. To reply, visit:

On March 20, 2013, 12:16 a.m., Rohini Palaniswamy wrote:

This is an automatically generated e-mail. To reply, visit:

(Updated March 20, 2013, 12:16 a.m.)

Review request for pig.


1) Fixed cases where partition pushdown was not happening for AND and OR construct
2) Commented out the negative test cases as they were actually not asserting anything.

This addresses bug PIG-3173.

----- 1458047 1458047



Unit tests added and tested few cases manually with hcat.


Rohini Palaniswamy

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 4 of 6 | next ›
Discussion Overview
groupdev @
categoriespig, hadoop
postedMar 20, '13 at 12:16a
activeApr 29, '13 at 8:51p



site design / logo © 2021 Grokbase