You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/12/24 13:20:50 UTC
[jira] [Updated] (SPARK-12056) NewHadoopRDD: TaskAttemptContext
should be created only after calling setConf.
[ https://issues.apache.org/jira/browse/SPARK-12056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-12056:
------------------------------
Fix Version/s: (was: 1.6.1)
1.6.0
> NewHadoopRDD: TaskAttemptContext should be created only after calling setConf.
> ------------------------------------------------------------------------------
>
> Key: SPARK-12056
> URL: https://issues.apache.org/jira/browse/SPARK-12056
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.5.2
> Reporter: Anderson de Andrade
> Assignee: Anderson de Andrade
> Priority: Minor
> Fix For: 1.6.0
>
>
> TaskAttemptContext's constructor will clone the configuration instead of referencing it. Calling setConf after creating TaskAttemptContext makes any changes to the configuration inside setConf unperceived by RecordReader instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org