[
https://issues.apache.org/jira/browse/FLINK-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15043989#comment-15043989
]
ASF GitHub Bot commented on FLINK-2488:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/1386#discussion_r46773625
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/broadcast/BroadcastVariableMaterialization.java
---
@@ -85,9 +85,9 @@ public void materializeVariable(MutableReader<?> reader,
TypeSerializerFactory<?
if (!references.add(referenceHolder)) {
throw new IllegalStateException(
String.format("The task %s
(%d/%d) already holds a reference to the broadcast variable %s.",
-
referenceHolder.getEnvironment().getTaskName(),
-
referenceHolder.getEnvironment().getIndexInSubtaskGroup() + 1,
-
referenceHolder.getEnvironment().getNumberOfSubtasks(),
+
referenceHolder.getEnvironment().getTaskInfo().getTaskName(),
--- End diff --
Can replace this with `getTaskInfo().getTaskNameWithSubtasks()`.
> 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)
