[
https://issues.apache.org/jira/browse/PIG-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025387#comment-16025387
]
Daniel Dai commented on PIG-4662:
---------------------------------
I don't think it would make noticeable performance difference going either way.
I'd like to see a modular design rather than intermingle different concept
together. Also I don't feel it is hard to find the join key in the logical
optimizer and adding a filter on it.
> New optimizer rule: filter nulls before inner joins
> ---------------------------------------------------
>
> Key: PIG-4662
> URL: https://issues.apache.org/jira/browse/PIG-4662
> Project: Pig
> Issue Type: Improvement
> Reporter: Ido Hadanny
> Assignee: Satish Subhashrao Saley
> Priority: Minor
> Labels: Performance
> Fix For: 0.18.0
>
>
> As stated in the docs, rewriting an inner join and filtering nulls from
> inputs can be a big performance gain:
> http://pig.apache.org/docs/r0.14.0/perf.html#nulls
> We would like to add an optimizer rule which detects inner joins, and filters
> nulls in all inputs:
> A = filter A by t is not null;
> B = filter B by x is not null;
> C = join A by t, B by x;
> see also:
> http://stackoverflow.com/questions/32088389/is-the-pig-optimizer-filtering-nulls-before-joining
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
