[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013829#comment-15013829
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
GitHub user sachingoel0101 opened a pull request:
https://github.com/apache/flink/pull/1386
[FLINK-2488] Expose Attempt Number in RuntimeContext
Passes the attempt number all the way from `TaskDeploymentDescriptor` to
the `RuntimeContext`.
Small thing I want to confirm: For `RuntimeContext` in Tez, is it okay to
use `TaskContext#getTaskAttemptNumber` provided by Tez as a proxy for the
attempt number?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sachingoel0101/flink attempt_number
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1386.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1386
----
commit c7b28bbf7d40b8571ee18d1d525535ab5ed523ca
Author: Sachin Goel <sachingoel0...@gmail.com>
Date: 2015-11-19T16:38:15Z
[FLINK-2488] Expose Attempt Number in RuntimeContext
----
> Expose attemptNumber in RuntimeContext
> --------------------------------------
>
> Key: FLINK-2488
> URL: https://issues.apache.org/jira/browse/FLINK-2488
> Project: Flink
> Issue Type: Improvement
> Components: JobManager, TaskManager
> Affects Versions: 0.10.0
> Reporter: Robert Metzger
> Assignee: Sachin Goel
> Priority: Minor
>
> It would be nice to expose the attemptNumber of a task in the
> {{RuntimeContext}}.
> This would allow user code to behave differently in restart scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
