[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699342#comment-14699342
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1026#issuecomment-131768999
Yes. Minimizing the arguments being passed to `RuntimeContext` was the
motivation. I thought about putting every task specific field into the TaskInfo
object but since it isn't a real problem, hesitated.
Should I do that then? I certainly like the idea. The constructors for
`RuntimeContext` are somewhat messy, and doing this would make any future
changes to contexts a lot easier.
> 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)
