[jira] [Comment Edited] (TEZ-4146) Register RUNNING state in DAG's state change callback

["Gopal Vijayaraghavan (Jira)" <ji...@apache.org>]

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

Gopal Vijayaraghavan edited comment on TEZ-4146 at 4/14/20, 8:10 PM:
---------------------------------------------------------------------

[~rajesh.balamohan]: this LGTM +1 tests pending, but can you rename the {{dagCompletionCondition}} to a different name, so that the meaning is retained?

The signal on that doesn't imply completion anymore.


was (Author: gopalv):
[~rajesh.balamohan]: this LGTM, but can you rename the {{dagCompletionCondition}} to a different name, so that the meaning is retained?

The signal on that doesn't imply completion anymore.

> Register RUNNING state in DAG's state change callback
> -----------------------------------------------------
>
>                 Key: TEZ-4146
>                 URL: https://issues.apache.org/jira/browse/TEZ-4146
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Minor
>         Attachments: TEZ-4146.1.patch, TEZ-4146.2.patch
>
>
> It would be good to register RUNNING in the DAG state change callbacks. This would help applications like Hive, when it [monitors the job|https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/monitoring/TezJobMonitor.java#L182] continuously for getting runtime breakdown at the end of the job..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)