[
https://issues.apache.org/jira/browse/PIG-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Le Dem updated PIG-2659:
-------------------------------
Attachment: PIG-2659_d.patch
PIG-2659_d.patch
adds logging as in PIG-2688
> add source location of the aliases in the physical plan
> -------------------------------------------------------
>
> Key: PIG-2659
> URL: https://issues.apache.org/jira/browse/PIG-2659
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Reporter: Julien Le Dem
> Assignee: Julien Le Dem
> Attachments: PIG-2659.patch, PIG-2659_a.patch, PIG-2659_b.patch,
> PIG-2659_c.patch, PIG-2659_d.patch
>
>
> The goal is to provide better information about what is actually running in a
> job.
> In particular when alias names are being reused.
> For example with the following script:
> {code}
> A = LOAD 'foo' using PigStorage();
> B = GROUP A BY $0;
> A = FOREACH B GENERATE COUNT(A);
> STORE A INTO 'bar';
> {code}
> The job conf will contain the following information
> {code}
> pig.alias.location: M: A[1,4],A[3,4],B[2,4] C: A[3,4],B[2,4] R: A[3,4]
> {code}
> A caveat is that the Logical Plan Optimizer throws away the original
> information when merging Logical Operators.
> this is already the case today with pig.alias
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
