[ https://issues.apache.org/jira/browse/PIG-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185081#comment-14185081 ]
Eyal Allweil commented on PIG-2836: ----------------------------------- I didn't try 0.13 - I had trouble setting it up, I ran into a problem similar to what is described in [this StackOverflow question.|http://stackoverflow.com/questions/25107734/pig-0-13-error-2998-unhandled-internal-error-org-apache-hadoop-mapreduce-task] (but that's a different story). I did confirm that this problem occurs on Pig 0.12.1. As for [PIG-3581|https://issues.apache.org/jira/browse/PIG-3581] - I'm not sure it's the same issue. Does Pig use the wrong value of *C* within the brackets, or overwrite it? From the description of that issue I assumed the problem was the resolution within the brackets, but in this issue the problem is that the alias gets overwritten, which affects the calling script in a worse, indirect way (because the return value is what was intended; i.e., the macro "works" correctly other than the overwriting). If we are talking about the same issue, then at the very least I would edit the "Fix Version" field of this issue to reflect that it was fixed in 0.13 - I don't have permissions to change this, probably because the issue was closed, but this will help people who stumble on this issue in the future. > Namespace in Pig macros collides with Pig scripts > ------------------------------------------------- > > Key: PIG-2836 > URL: https://issues.apache.org/jira/browse/PIG-2836 > Project: Pig > Issue Type: Bug > Components: grunt, parser > Affects Versions: 0.9.2, 0.10.0, 0.11, 0.10.1 > Reporter: Russell Jurney > Assignee: Alan Gates > Priority: Critical > Labels: bacon, confit, goto, hash, macros, pig, sad > > Relation names in macros collide with relation names in the calling pig > script. This is my most common source of errors and it makes writing macros > hard. Suggest that the macro processor create a unique namespace for all > relations in a macro other than $in and $out. Prepend something to each > relation name or somehow create a unique per-macro namespace. > This may conflict with some uses of macros where relation names are passed > through passively, but this is always avoidable by supplying parameters and > feels GOTO f*cked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)