Return-Path: X-Original-To: apmail-pig-dev-archive@www.apache.org Delivered-To: apmail-pig-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57452116D1 for ; Mon, 14 Apr 2014 11:03:21 +0000 (UTC) Received: (qmail 3258 invoked by uid 500); 14 Apr 2014 11:03:17 -0000 Delivered-To: apmail-pig-dev-archive@pig.apache.org Received: (qmail 2778 invoked by uid 500); 14 Apr 2014 11:03:17 -0000 Mailing-List: contact dev-help@pig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pig.apache.org Delivered-To: mailing list dev@pig.apache.org Received: (qmail 2748 invoked by uid 500); 14 Apr 2014 11:03:15 -0000 Delivered-To: apmail-hadoop-pig-dev@hadoop.apache.org Received: (qmail 2742 invoked by uid 99); 14 Apr 2014 11:03:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2014 11:03:15 +0000 Date: Mon, 14 Apr 2014 11:03:14 +0000 (UTC) From: "Lorand Bendig (JIRA)" To: pig-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (PIG-3888) Direct fetch doesn't differentiate between frontend and backend sides MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PIG-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorand Bendig updated PIG-3888: ------------------------------- Status: Patch Available (was: Open) > Direct fetch doesn't differentiate between frontend and backend sides > --------------------------------------------------------------------- > > Key: PIG-3888 > URL: https://issues.apache.org/jira/browse/PIG-3888 > Project: Pig > Issue Type: Bug > Reporter: Lorand Bendig > Assignee: Lorand Bendig > Attachments: PIG-3888.patch > > > While testing PIG-3558, I found that fetch mode doesn't set the task id in the jobconf before running. As a consequence, {{UdfContext#isFrontend()}} will always return true. Loaders and Storers which initialize themselves based on this flag may fail. -- This message was sent by Atlassian JIRA (v6.2#6252)