[
https://issues.apache.org/jira/browse/PIG-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453471#comment-16453471
]
Koji Noguchi commented on PIG-5335:
-----------------------------------
{quote}
Maybe a silly question but asking Daniel Dai. Can ProjectStarExpander and
ProjStarInUdfExpander be moved from LogicalPlanBuilder to
LogicalPlan.validate() ?
{quote}
First tried this but saw that many tests from LOCube and others started failing
since these LogicalOperator depended on having these range expanded at creation
time. I could have tried to move most of LogicalPlanBuilder steps to
LogicalPlan.validate() but that would be too much work for the minor jira with
just error message fixing.
> 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
>
> {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)
