You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2014/08/03 05:20:11 UTC

[jira] [Updated] (TEZ-1072) Consolidate monitoring APIs in DAGClient

     [ https://issues.apache.org/jira/browse/TEZ-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Eagles updated TEZ-1072:
---------------------------------

    Attachment: TEZ-1072-DAGCLIENTUTILS-v1.patch

Patch doesn't consolidate the monitoring, but shows how the dag monitoring could be a separate entity.

> Consolidate monitoring APIs in DAGClient
> ----------------------------------------
>
>                 Key: TEZ-1072
>                 URL: https://issues.apache.org/jira/browse/TEZ-1072
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Priority: Blocker
>              Labels: api
>         Attachments: TEZ-1072-DAGCLIENTUTILS-v1.patch
>
>
> Rename waitForCompletionWithAllStatusUpdates - was this meant to be waitForCompletionWithAllVertexUpdates
> Reduce the number of methods exposed - waitForCompletion, waitForCompletionWithStatusUpdates(@Nullable Set<Vertex> vertices,
>       @Nullable Set<StatusGetOpts> statusGetOpts), waitForCompletionWithAllStatusUpdates(@Nullable Set<StatusGetOpts> statusGetOpts)



--
This message was sent by Atlassian JIRA
(v6.2#6252)