[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035761#comment-15035761
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1386#issuecomment-161286037
This generally looks good and pretty straight forward.
As such it is actually good to merge.
I remember that a while back, we were discussing to create a `TaskInfo`
object that would contain "subtaskIndex", "parallelism", "name",
"name-with-subtask", "attempt", "vertex id", "attempt id", etc...
Having such an object would allow to pass all these elements simply from
the TaskDeploymentDescriptor to the Task to the RuntimeContext. And whenever we
add another field, we need not propagate it manually through all the functions
calls, but simply add it to the TaskInfo.
What do you think?
> 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)
