You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Navneet Kapur (JIRA)" <ji...@apache.org> on 2012/12/13 03:27:20 UTC

[jira] [Created] (PIG-3094) ERROR 2229: Couldn't find matching uid -1 in Pig 0.10.0

Navneet Kapur created PIG-3094:
----------------------------------

             Summary:  ERROR 2229: Couldn't find matching uid -1 in Pig 0.10.0
                 Key: PIG-3094
                 URL: https://issues.apache.org/jira/browse/PIG-3094
             Project: Pig
          Issue Type: Bug
            Reporter: Navneet Kapur
             Fix For: 0.10.0


I'm getting the error message:
ERROR org.apache.pig.tools.grunt.Grunt - ERROR 2229: Couldn't find matching uid -1 for project (Name: Project Type: bytearray Uid: 2754 Input: 0 Column: 4)

This seems to have been solved for versions 0.8 and 0.9. https://issues.apache.org/jira/browse/PIG-1979

For privacy reasons, I am unable to post the code here. The stack-trace that I get is as follows:
Pig Stack Trace
---------------
ERROR 2229: Couldn't find matching uid -1 for project (Name: Project Type: bytearray Uid: 2754 Input: 0 Column: 4)

org.apache.pig.impl.logicalLayer.FrontendException: ERROR 2000: Error processing rule ColumnMapKeyPrune. Try -t ColumnMapKeyPrune
    at org.apache.pig.newplan.optimizer.PlanOptimizer.optimize(PlanOptimizer.java:122)
    at org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.compile(HExecutionEngine.java:282)
    at org.apache.pig.PigServer.compilePp(PigServer.java:1316)
    at org.apache.pig.PigServer.executeCompiledLogicalPlan(PigServer.java:1253)
    at org.apache.pig.PigServer.execute(PigServer.java:1245)
    at org.apache.pig.PigServer.executeBatch(PigServer.java:362)
    at org.apache.pig.tools.grunt.GruntParser.executeBatch(GruntParser.java:132)
    at org.apache.pig.tools.grunt.GruntParser.parseStopOnError(GruntParser.java:193)
    at org.apache.pig.tools.grunt.GruntParser.parseStopOnError(GruntParser.java:165)
    at org.apache.pig.tools.grunt.Grunt.exec(Grunt.java:84)
    at org.apache.pig.Main.run(Main.java:555)
    at org.apache.pig.Main.main(Main.java:111)
Caused by: org.apache.pig.impl.logicalLayer.FrontendException: ERROR 2229: Couldn't find matching uid -1 for project (Name: Project Type: bytearray Uid: 2754 Input: 0 Column: 4)
    at org.apache.pig.newplan.logical.optimizer.ProjectionPatcher$ProjectionRewriter.visit(ProjectionPatcher.java:91)
    at org.apache.pig.newplan.logical.expression.ProjectExpression.accept(ProjectExpression.java:207)
    at org.apache.pig.newplan.DepthFirstWalker.depthFirst(DepthFirstWalker.java:64)
    at org.apache.pig.newplan.DepthFirstWalker.walk(DepthFirstWalker.java:53)
    at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:50)
    at org.apache.pig.newplan.logical.optimizer.AllExpressionVisitor.visit(AllExpressionVisitor.java:136)
    at org.apache.pig.newplan.logical.relational.LOInnerLoad.accept(LOInnerLoad.java:128)
    at org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
    at org.apache.pig.newplan.logical.optimizer.AllExpressionVisitor.visit(AllExpressionVisitor.java:114)
    at org.apache.pig.newplan.logical.relational.LOForEach.accept(LOForEach.java:75)
    at org.apache.pig.newplan.DependencyOrderWalker.walk(DependencyOrderWalker.java:75)
    at org.apache.pig.newplan.PlanVisitor.visit(PlanVisitor.java:50)
    at org.apache.pig.newplan.logical.optimizer.ProjectionPatcher.transformed(ProjectionPatcher.java:48)
    at org.apache.pig.newplan.optimizer.PlanOptimizer.optimize(PlanOptimizer.java:113)
    ... 11 more
================================================================================


Further notes:
1. I experimented with removing the FOREACH...GENERATE statement where this error seems to be occurring. But then, I get the error message:

ERROR 2270: Logical plan invalid state: duplicate uid in schema

2. When I ran the script with the argument-option `-t ColumnMapKeyPrune`, the script did successfully run albeit very slowly.

--
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