[
https://issues.apache.org/jira/browse/PIG-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270887#comment-13270887
]
Doug Daniels commented on PIG-2689:
-----------------------------------
Attached a patch that fixes this by copying the signature to the new POStore.
It also copies the alias, which helps in illustrate.
> JsonStorage fails to find schema when LimitAdjuster runs
> --------------------------------------------------------
>
> Key: PIG-2689
> URL: https://issues.apache.org/jira/browse/PIG-2689
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Doug Daniels
> Attachments: PIG-2689.patch
>
>
> Scripts that both save out data with JsonStorage and trigger the
> LimitAdjuster (e.g. doing an order by followed by a limit) yield the
> following Exception:
> java.io.IOException: Could not find schema in UDF context
> at
> org.apache.pig.builtin.JsonStorage.prepareToWrite(JsonStorage.java:125)
> at
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat$PigRecordWriter.<init>(PigOutputFormat.java:125)
> at
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat.getRecordWriter(PigOutputFormat.java:86)
> at
> org.apache.hadoop.mapred.ReduceTask$NewTrackingRecordWriter.<init>(ReduceTask.java:569)
> at
> org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:638)
> at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:417)
> at
> org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:260)
> This happens b/c the LimitAdjuster does not copy the signature into it's
> newly created POStore, and hence JsonStorage looks for the schema for a null
> signature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
