You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@pig.apache.org by Vadim Zaliva <kr...@gmail.com> on 2009/02/26 21:31:24 UTC
Attempt to access field which was not found in the input
I see a lot of warnings like this in my task logs (trunk version)
running in mapreduce mode:
ne.physicalLayer.expressionOperators.POProject: Attempt to access
field which was not found in the input
2009-02-26 12:19:19,871 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
2009-02-26 12:19:20,469 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
2009-02-26 12:19:20,469 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
2009-02-26 12:19:20,469 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
2009-02-26 12:19:24,544 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
2009-02-26 12:19:24,544 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
2009-02-26 12:19:24,544 WARN
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject:
Attempt to access field which was not found in the input
I have not seen anything like this running on smaller data set in
local mode. Any suggestions what may be causing these?
Vadim