[jira] Updated: (MAPREDUCE-1486) Configuration data should be preserved within the same MapTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom White updated MAPREDUCE-1486: - Status: Open (was: Patch Available) Cancelling while feedback is addressed. > Configuration data should be preserved within the same MapTask > -- > > Key: MAPREDUCE-1486 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1486 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: task >Reporter: Aaron Kimball >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1486.patch > > > Map tasks involve a number of Contexts -- at least a TaskAttemptContext and a > MapContext. These context objects contain a Configuration each; when one > context is initialized, it initializes its own Configuration by deep-copying > a previous Configuration. > If one Context instance is used entirely prior to a second, more specific > Context then the second Context should contain the configuration data > initialized in the previous Context. This specifically affects the > interaction between an InputFormat and its RecordReader instance(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1486) Configuration data should be preserved within the same MapTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1486: - Status: Open (was: Patch Available) > Configuration data should be preserved within the same MapTask > -- > > Key: MAPREDUCE-1486 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1486 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: task >Reporter: Aaron Kimball >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1486.patch > > > Map tasks involve a number of Contexts -- at least a TaskAttemptContext and a > MapContext. These context objects contain a Configuration each; when one > context is initialized, it initializes its own Configuration by deep-copying > a previous Configuration. > If one Context instance is used entirely prior to a second, more specific > Context then the second Context should contain the configuration data > initialized in the previous Context. This specifically affects the > interaction between an InputFormat and its RecordReader instance(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1486) Configuration data should be preserved within the same MapTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1486: - Status: Patch Available (was: Open) recycling hudson to check TestJobOutputCommitter > Configuration data should be preserved within the same MapTask > -- > > Key: MAPREDUCE-1486 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1486 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: task >Reporter: Aaron Kimball >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1486.patch > > > Map tasks involve a number of Contexts -- at least a TaskAttemptContext and a > MapContext. These context objects contain a Configuration each; when one > context is initialized, it initializes its own Configuration by deep-copying > a previous Configuration. > If one Context instance is used entirely prior to a second, more specific > Context then the second Context should contain the configuration data > initialized in the previous Context. This specifically affects the > interaction between an InputFormat and its RecordReader instance(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1486) Configuration data should be preserved within the same MapTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1486: - Attachment: MAPREDUCE-1486.patch Attaching patch which fixes this problem; now the same configuration data will flow forward through the map task. This patch also contains a test case that highlights the problem. > Configuration data should be preserved within the same MapTask > -- > > Key: MAPREDUCE-1486 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1486 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: task >Reporter: Aaron Kimball >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1486.patch > > > Map tasks involve a number of Contexts -- at least a TaskAttemptContext and a > MapContext. These context objects contain a Configuration each; when one > context is initialized, it initializes its own Configuration by deep-copying > a previous Configuration. > If one Context instance is used entirely prior to a second, more specific > Context then the second Context should contain the configuration data > initialized in the previous Context. This specifically affects the > interaction between an InputFormat and its RecordReader instance(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1486) Configuration data should be preserved within the same MapTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1486: - Status: Patch Available (was: Open) > Configuration data should be preserved within the same MapTask > -- > > Key: MAPREDUCE-1486 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1486 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: task >Reporter: Aaron Kimball >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1486.patch > > > Map tasks involve a number of Contexts -- at least a TaskAttemptContext and a > MapContext. These context objects contain a Configuration each; when one > context is initialized, it initializes its own Configuration by deep-copying > a previous Configuration. > If one Context instance is used entirely prior to a second, more specific > Context then the second Context should contain the configuration data > initialized in the previous Context. This specifically affects the > interaction between an InputFormat and its RecordReader instance(s). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
