[
https://issues.apache.org/jira/browse/PIG-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005119#comment-14005119
]
Rohini Palaniswamy commented on PIG-3946:
-----------------------------------------
Looks good. But isn't there a better way to determine what is the input to
POValueInputTez by selecting one that is not a scalar input? Can't we do set
the correct input for POValueInputTez in TezCompiler itself?
> Fix e2e test failure CastScalar_11
> ----------------------------------
>
> Key: PIG-3946
> URL: https://issues.apache.org/jira/browse/PIG-3946
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: tez-branch
>
> Attachments: PIG-3946-1.patch
>
>
> Stack:
> Error: java.lang.NullPointerException
> : at java.io.FileOutputStream.writeBytes(Native Method)
>
> : at
> java.io.FileOutputStream.write(FileOutputStream.java:282)
>
> : at
> org.apache.tez.runtime.library.common.shuffle.impl.InMemoryReader.dumpOnError(InMemoryReader.java:85)
> : at
> org.apache.tez.runtime.library.common.shuffle.impl.InMemoryReader.readRawKey(InMemoryReader.java:119)
> : at
> org.apache.tez.runtime.library.common.sort.impl.IFile$Reader.nextRawKey(IFile.java:510)
>
> : at
> org.apache.tez.runtime.library.common.readers.ShuffledUnorderedKVReader.readNextFromCurrentReader(ShuffledUnorderedKVReader.java:147)
> : at
> org.apache.tez.runtime.library.common.readers.ShuffledUnorderedKVReader.next(ShuffledUnorderedKVReader.java:108)
> : at
> org.apache.pig.backend.hadoop.executionengine.tez.POValueInputTez.getNextTuple(POValueInputTez.java:123)
> : at
> org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:300)
> : at
> org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POFilter.getNextTuple(POFilter.java:91)
> : at
> org.apache.pig.backend.hadoop.executionengine.physicalLayer.PhysicalOperator.processInput(PhysicalOperator.java:300)
> : at
> org.apache.pig.backend.hadoop.executionengine.tez.POStoreTez.getNextTuple(POStoreTez.java:113)
>
> : at
> org.apache.pig.backend.hadoop.executionengine.tez.PigProcessor.runPipeline(PigProcessor.java:276)
> : at
> org.apache.pig.backend.hadoop.executionengine.tez.PigProcessor.run(PigProcessor.java:175)
>
> : at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:307)
>
> : at
> org.apache.hadoop.mapred.YarnTezDagChild$5.run(YarnTezDagChild.java:581)
>
> : at java.security.AccessController.doPrivileged(Native
> Method)
> : at javax.security.auth.Subject.doAs(Subject.java:394)
>
> : at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1495)
>
> : at
> org.apache.hadoop.mapred.YarnTezDagChild.main(YarnTezDagChild.java:570)
>
> : ], Vertex failed as one or more tasks failed.
> failedTasks:1]
> : Vertex killed, vertexName=scope-97
> The reason is in a vertex, we have two POValueInput, and Pig erroneously
> assign them to the same input vertex.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
