You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2018/01/02 15:33:00 UTC
[jira] [Resolved] (SPARK-22897) Expose stageAttemptId in
TaskContext
[ https://issues.apache.org/jira/browse/SPARK-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-22897.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request 20082
[https://github.com/apache/spark/pull/20082]
> Expose stageAttemptId in TaskContext
> -------------------------------------
>
> Key: SPARK-22897
> URL: https://issues.apache.org/jira/browse/SPARK-22897
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 2.1.2, 2.2.1
> Reporter: Xianjin YE
> Assignee: Xianjin YE
> Priority: Minor
> Fix For: 2.3.0
>
>
> Currently, there's no easy way for Executor to detect a new stage is launched as stageAttemptId is missing.
> I'd like to propose exposing stageAttemptId in TaskContext, and will send a pr if community thinks it's a good thing.
> cc [~cloud_fan]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org