You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/11/30 21:55:11 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15032439#comment-15032439 ] 

Apache Spark commented on SPARK-12056:
--------------------------------------

User 'adeandrade' has created a pull request for this issue:
https://github.com/apache/spark/pull/10046

> 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
>            Priority: Minor
>
> 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