You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org> on 2012/09/10 18:50:08 UTC
[jira] [Commented] (PIG-2912) Pig should clone JobConf while
creating JobContextImpl and TaskAttemptContextImpl in Hadoop23
[ https://issues.apache.org/jira/browse/PIG-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452137#comment-13452137 ]
Dmitriy V. Ryaboy commented on PIG-2912:
----------------------------------------
Could you create a test in which the storage or loader function uses UDFContext to ship around information? I don't think the current test probes the issue that caused us to roll back PIG-2578
> Pig should clone JobConf while creating JobContextImpl and TaskAttemptContextImpl in Hadoop23
> ---------------------------------------------------------------------------------------------
>
> Key: PIG-2912
> URL: https://issues.apache.org/jira/browse/PIG-2912
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.9.3, 0.10.1
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.9.3, 0.11, 0.10.1
>
> Attachments: PIG-2912-branch09.patch, PIG-2912-branch10.patch, PIG-2912-trunk.patch
>
>
> There is change in the semantics of
> JobContext::JobContext(Configuration, JobID). While in .20, the Config was
> cloned, in .23 the Config is adopted (if it's a JobConf). This causes the same
> Configuration instance to be written-to for different tables in the same job.
> It would affect multi store commands in pig on Hadoop 23/2.0. The
> cloning in HadoopShims was part of PIG-2578 but was reverted to other issues.
--
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