[
https://issues.apache.org/jira/browse/PIG-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791070#comment-13791070
]
Cheolsoo Park commented on PIG-3461:
------------------------------------
[~aniket486], can you take a look at PIG-3510? I discovered it after deploying
this new partition filter optimizer to production today. It seems that
optimization rules are applied in a different order than before. Particularly
in my case, MergeFilter used to come *before* PartionFilterPushDown, but now it
comes *after* NewPartitionFilterPushDown. I didn't expect this side effect, but
it seems like a serious regression.
> Rewrite PartitionFilterOptimizer to make it work for all the cases
> ------------------------------------------------------------------
>
> Key: PIG-3461
> URL: https://issues.apache.org/jira/browse/PIG-3461
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.11.1
> Reporter: Aniket Mokashi
> Assignee: Aniket Mokashi
> Fix For: 0.12.0
>
> Attachments: PIG-3461-2.patch, PIG-3461-4.patch, PIG-3461-6.patch
>
>
> Current algorithm for Partition Filter pushdown identification fails in
> several corner cases. We need to rewrite its logic so that it works in all
> cases and does the maximum possible filter pushdown.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
