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 04:02:12 UTC
[jira] [Commented] (TEZ-1072) Consolidate monitoring APIs in
DAGClient
[ https://issues.apache.org/jira/browse/TEZ-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083837#comment-14083837 ]
Jonathan Eagles commented on TEZ-1072:
--------------------------------------
Perhaps, instead of providing these API as part of DAGClient, could these be provided as utility functions as part of a new DAGClientUtils. Having this separation will clarify what APIs and functionalities belong as part of DAGClient and which do not.
> 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
>
> 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)