[PIG-4897] Scope of param substitution for run/exec commands

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.17.0
• Hadoop Flags: Incompatible change, Reviewed
• Release Note: With run/exec command, parameters are now scoped and caller would not see the parameters declared within the callee's scripts.
• Assignee: Koji Noguchi
• Reporter: Koji Noguchi
• Created: 16/May/16 22:09
• Updated: 21/Jun/17 09:15
• Resolved: 10/Jan/17 21:15

Description

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.

test1.pig

exec -param output=/tmp/deleteme111 test1_1.pig
exec -param output=/tmp/deleteme222 test1_1.pig

test1_1.pig

%default myout '$output.out';
A = load 'input.txt' as (a0:int);
store A into '$myout';

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

Issue Links

• is broken by: PIG-3359 Register Statements and Param Substitution in Macros
• relates to: PIG-5028 Param expansion in macro is confusing