[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699349#comment-14699349
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1026#issuecomment-131771732
Yes, let's have a `TaskRuntimeInfo` and a `TaskManagerContext`. Both are
available in the `RuntimeEnvironment` and passed to the `RuntimeContext`.
The `TaskRuntimeInfo` has all task-specific information, the
`TaskManagerContext` all cross-task constant parts. It could also hold the I/O
manager, memory manager, ...
> 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
> 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)
