You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/01/20 19:13:35 UTC
[jira] [Comment Edited] (SPARK-4014) TaskContext.attemptId returns
taskId
[ https://issues.apache.org/jira/browse/SPARK-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284137#comment-14284137 ]
Josh Rosen edited comment on SPARK-4014 at 1/20/15 6:12 PM:
------------------------------------------------------------
Note to self: when backporting this to any branches, also backport SPARK-5333 (since that fixes a bug introduced here).
was (Author: joshrosen):
Note to self: when backporting this to any branches, also backport SPARK-4014 (since that fixes a bug introduced here).
> TaskContext.attemptId returns taskId
> ------------------------------------
>
> Key: SPARK-4014
> URL: https://issues.apache.org/jira/browse/SPARK-4014
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: Yin Huai
> Assignee: Josh Rosen
> Priority: Minor
> Labels: backport-needed
> Fix For: 1.3.0
>
>
> In TaskRunner, we assign the taskId of a task to the attempId of the corresponding TaskContext. Should we rename attemptId to taskId to avoid confusion?
--
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