[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037702#comment-15037702
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1386#issuecomment-161608168
As far as I can see from these changes, introducing a `TaskInfo` will
completely subsume this change here and change every line again.
You are right, usually different issues should go into different pull
requests. But here, one change is a superset of the other change, so that the
"task attempt" change without the "task info" change becomes obsolete.
I am not strictly against merging this, just thinking that it makes sense
to put the TaskInfo into this change as well...
> 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)
