Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Wed, 25 Feb 2015 17:51:04 +0000 (UTC)
From: "Brian Johnson (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12772152.1422998990000.12736.1424886664769@Atlassian.JIRA>
In-Reply-To: <JIRA.12772152.1422998990000@Atlassian.JIRA>
References: <JIRA.12772152.1422998990000@Atlassian.JIRA>
 <JIRA.12772152.1422998990870@arcas>
Subject: [jira] [Commented] (PIG-4408) Merge join should support replicated
 join as a predecessor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/PIG-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336850#comment-14336850 ] 

Brian Johnson commented on PIG-4408:
------------------------------------

It looks like only one of them needs to change to STATUS_NULL at line 402. I'm running all the tests again and then I'll resubmit the patch

> 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)