Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Fri, 9 Sep 2016 20:37:20 +0000 (UTC)
From: "Koji Noguchi (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12970170.1463436556000.535223.1473453440513@Atlassian.JIRA>
In-Reply-To: <JIRA.12970170.1463436556000@Atlassian.JIRA>
References: <JIRA.12970170.1463436556000@Atlassian.JIRA> <JIRA.12970170.1463436556090@arcas>
Subject: [jira] [Updated] (PIG-4897) Scope of param substitution for
 run/exec commands
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 09 Sep 2016 20:37:22 -0000


     [ https://issues.apache.org/jira/browse/PIG-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koji Noguchi updated PIG-4897:
------------------------------
    Attachment: pig-4897-v06.patch

{quote}
Makes sense. We can just go with the current patch which keeps things simple and clear. testScopeOfParamWithNestedRunCommand is in v04 patch but missing in v05 though. Can you also create a new jira for the macro case and update the comment for the testScopeOfParamWithMacro with that jira number.
{quote}
Thanks Rohini.
Added back testScopeOfParamWithNestedRunCommand, created PIG-5028 for tracking the macro issue and updated the comment in testScopeOfParamWithMacro.

> Scope of param substitution for run/exec commands
> -------------------------------------------------
>
>                 Key: PIG-4897
>                 URL: https://issues.apache.org/jira/browse/PIG-4897
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Koji Noguchi
>            Assignee: Koji Noguchi
>         Attachments: pig-4897-v01-notestyet.patch, pig-4897-v02.patch, pig-4897-v03.patch, pig-4897-v04.patch, pig-4897-v05.patch, pig-4897-v06.patch
>
>
> After PIG-3359, pig param substitution became global in that parameter declared in the pig script called from {{run}} or {{exec}} would live after that script finishes.  
> This created an interesting situation.
> {code:title=test1.pig}
> exec -param output=/tmp/deleteme111 test1_1.pig
> exec -param output=/tmp/deleteme222 test1_1.pig
> {code}
> {code:title=test1_1.pig}
> %default myout '$output.out';
> A = load 'input.txt' as (a0:int);
> store A into '$myout';
> {code}
> Running {{test1.pig}} would try to run two jobs that both tries to write to /tmp/deleteme111 and fail.  (Second param output=/tmp/deleteme222 is ignored.)


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