[
https://issues.apache.org/jira/browse/PIG-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336462#comment-14336462
]
Brian Johnson commented on PIG-4408:
------------------------------------
The included test case fails without the change with the wrong count. I can't
remember exactly now, but I believe with only one record in the LHS of the
merge it will not produce any output at all. It still eventually gets to EOP
now, but like in PIG-4166 this forces another pass to get any records which are
"cached" waiting for the LHS key to change before outputting. I think there was
actually a bug in it before this change.
> 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.14.1
>
> Attachments: 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)
