You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sachin Goel (JIRA)" <ji...@apache.org> on 2015/08/16 11:00:52 UTC

[jira] [Commented] (FLINK-2524) Add "getTaskNameWithSubtasks()" to RuntimeContext

    [ https://issues.apache.org/jira/browse/FLINK-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698594#comment-14698594 ] 

Sachin Goel commented on FLINK-2524:
------------------------------------

Implemented in https://github.com/apache/flink/pull/970

> Add "getTaskNameWithSubtasks()" to RuntimeContext
> -------------------------------------------------
>
>                 Key: FLINK-2524
>                 URL: https://issues.apache.org/jira/browse/FLINK-2524
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>    Affects Versions: 0.10
>            Reporter: Stephan Ewen
>            Assignee: Sachin Goel
>              Labels: easyfix, starter
>             Fix For: 0.10
>
>
> When printing information to logs or debug output, one frequently needs to identify the statement with the originating task (task name and which subtask).
> In many places, the system and user code manually construct something like "MyTask (2/7)".
> The {{RuntimeContext}} should offer this, because it is too frequently needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)