[
https://issues.apache.org/jira/browse/PIG-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345115#comment-14345115
]
Brian Johnson commented on PIG-4408:
------------------------------------
That's very strange. Daniel's patch looks like it's doing the same thing as my
original patch and all the tests passed for me for that as well as the second
patch I submitted. I created the test case that is failing for you and
submitted the patch for it with PIG-4166, what happens if you revert the change
to POCollectedGroup? Alternately we would use the second patch I submitted
which makes a much smaller change to the process.
> Merge join should support replicated join as a predecessor
> ----------------------------------------------------------
>
> Key: PIG-4408
> URL: https://issues.apache.org/jira/browse/PIG-4408
> Project: Pig
> Issue Type: New Feature
> Affects Versions: 0.14.0
> Reporter: Brian Johnson
> Assignee: Brian Johnson
> Fix For: 0.15.0
>
> Attachments: PIG-4408-3.patch, patch, patch
>
>
> Since a replicated join doesn't trigger a reduce or change the output
> ordering a merge join should work after it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
