[ https://issues.apache.org/jira/browse/PIG-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289823#comment-15289823 ]
Koji Noguchi commented on PIG-4897: ----------------------------------- A better example. {code:title=test10.pig} exec HADOOPPF-12103/test10_1.pig exec HADOOPPF-12103/test10_2.pig {code} {code:title=test10_1.pig} %default output '/tmp/deleteme111'; A = load 'input.txt' as (a0:int); store A into '$output'; --writes to /tmp/deleteme111 {code} {code:title=test10_2.pig} %default output '/tmp/deleteme222'; A = load 'input.txt' as (a0:int); store A into '$output'; --this tries to write to /tmp/deleteme111 unexpectedly. {code} > 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 > > 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)