Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Mon, 29 Sep 2014 18:18:34 +0000 (UTC)
From: "Daniel Dai (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12744136.1411680332000.147029.1412014714584@Atlassian.JIRA>
In-Reply-To: <JIRA.12744136.1411680332000@Atlassian.JIRA>
References: <JIRA.12744136.1411680332000@Atlassian.JIRA>
 <JIRA.12744136.1411680332845@arcas>
Subject: [jira] [Commented] (PIG-4202) UDFContext.isFrontend return true for
 OutputCommitter in local mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Dai commented on PIG-4202:
---------------------------------

Pig has a single PigOutputCommitter derived from mapreduce.OutputCommitter even when there are multiple HDFS outputs. PigOutputCommitter is a wrapper, and it will invoke individual OutputCommitter sequentially. We only experience static variable issue with PigOutputCommitter itself. If the wrapped OutputCommitter has its own static variable, yes, they might have some issues as well.

> UDFContext.isFrontend return true for OutputCommitter in local mode
> -------------------------------------------------------------------
>
>                 Key: PIG-4202
>                 URL: https://issues.apache.org/jira/browse/PIG-4202
>             Project: Pig
>          Issue Type: Bug
>          Components: impl
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 0.14.0
>
>         Attachments: PIG-4202-1.patch, PIG-4202-2.patch
>
>
> We switch to use UDFContext.isFrontend in PIG-4187. However, it does not work as expected in local mode. This causes some local mode test fail (TestOrcStoragePushdown.createInputData).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)