[
https://issues.apache.org/jira/browse/PIG-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489562#comment-13489562
]
Rohini Palaniswamy commented on PIG-2970:
-----------------------------------------
Koji,
The idea seems to be to keep the dangling nodes intact in the plan and do a
search for LOGenerate node in LOForeach every time we are trying to get it from
LOForEach. I don't prefer this approach much. If something is not used, it is
better to discard it instead of keeping it and stepping around it all the time.
The approach might work but not sure what it achieves or gives any benefit.
Also it is not efficient. I would prefer to stay with the original assumption
of LOGenerate is the only sink in nested plan. It keeps the plan simple, clean
and sticks to the intent of the execution. Can you give more info on why you
would like to keep the dangling nodes in the plan?
> Nested foreach getting incorrect schema when having unrelated inner query
> -------------------------------------------------------------------------
>
> Key: PIG-2970
> URL: https://issues.apache.org/jira/browse/PIG-2970
> Project: Pig
> Issue Type: Bug
> Components: parser
> Affects Versions: 0.10.0
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Priority: Minor
> Fix For: 0.11, 0.12
>
> Attachments: pig-2970-trunk-v01.txt, pig-2970-trunk-v02.txt
>
>
> While looking at PIG-2968, hit a weird error message.
> {noformat}
> $ cat -n test/foreach2.pig
> 1 daily = load 'nyse' as (exchange, symbol);
> 2 grpd = group daily by exchange;
> 3 unique = foreach grpd {
> 4 sym = daily.symbol;
> 5 uniq_sym = distinct sym;
> 6 --ignoring uniq_sym result
> 7 generate group, daily;
> 8 };
> 9 describe unique;
> 10 zzz = foreach unique generate group;
> 11 explain zzz;
> % pig -x local -t ColumnMapKeyPrune test/foreach2.pig
> ...
> unique: {symbol: bytearray}
> 2012-10-12 16:55:44,226 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
> 1025:
> <file test/foreach2.pig, line 10, column 30> Invalid field projection.
> Projected field [group] does not exist in schema: symbol:bytearray.
> ...
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
