pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koji Noguchi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-4897) Scope of param substitution for run/exec commands
Date Thu, 08 Sep 2016 21:01:21 GMT

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

Koji Noguchi commented on PIG-4897:

Thanks Rohini!  I'll create a new jira for the macro and patch shortly. 

But given this is an incompatible change if we have user depending on the global param behavior,
can I have one more +1?  [~daijy], appreciate if you could take a brief look.  (Not for the
patch itself but for the idea of making the parameters scoped for exec&run.)

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

View raw message