[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699623#comment-14699623
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1026#issuecomment-131853677
I have implemented a `TaskRuntimeInfo` which holds descriptive information
about the task, such as name, index, parallelism, etc. Also renamed the
`TaskManagerRuntimeInfo` to `TaskManagerContext` and included the `IOManager`,
`MemoryManager` and `NetworkEnvironment`.
The `RuntimeContext`s now use these two fields in their constructor.
Further, for minimizing number of changes while modifying the
`RuntimeContext`s in future, I have also modified the test classes to use a
*create runtime* utility function.
Waiting for travis to give the green light for now.
> 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)
