[
https://issues.apache.org/jira/browse/PIG-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472251#comment-16472251
]
Rohini Palaniswamy commented on PIG-5335:
-----------------------------------------
The patch is setting LogicalExpression.getNextUid() instead of leaving it at
default -1 unlike other cases. Can you provide the explanation for that here
and also upload a patch with a comment giving link to your jira explanation?
> Error message from range projection completely misleading
> ---------------------------------------------------------
>
> Key: PIG-5335
> URL: https://issues.apache.org/jira/browse/PIG-5335
> Project: Pig
> Issue Type: Bug
> Reporter: Koji Noguchi
> Assignee: Koji Noguchi
> Priority: Major
> Attachments: pig-5335-v01.patch
>
>
> {code}
> A = load 'input.txt' as (a0,a1,a2,a3);
> B = FOREACH A GENERATE a0, a1, a2, a3;
> store B into '/tmp/deleteme';
> C = FOREACH A GENERATE a0, b1, a2, a3;
> D = FOREACH C GENERATE a0..a2;
> (end of script, no store, nothing)
> {code}
> Error message
> {panel}
> 2018-04-10 10:22:33,360 \[main] ERROR org.apache.pig.PigServer - exception
> during parsing: Error during parsing. Invalid field projection. Projected
> field \[a0] does not exist in schema:
> a0:bytearray,a0:bytearray,a2:bytearray,a3:bytearray.
> {panel}
> At least two issues.
> # Error should be about FOREACH for C referencing non-existing field 'b1'.
> But the error message is saying something about 'a0'.
> # Script itself is not using relation C and D at all. It's confusing to see
> errors coming out of unused relations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
