[
https://issues.apache.org/jira/browse/TEZ-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049499#comment-15049499
]
Bikas Saha commented on TEZ-2981:
---------------------------------
What particular details are needed on from tasks. Not having task/attempt level
details in there was a deliberate decision to prevent a lot of low level data
being accessed via the DAGClient. It was targeted mainly as a lib to submit and
monitor DAGs to completion/failure. The Tez UI is the place for more detailed
investigations.
Alternatively, instead of changing DAGClient (that submit a DAG and interacts
with it) would it be better to create a TezATSLib that can fetch detailed ATS
data.
> extend DAGClient API: Give consumers access to the task data
> ------------------------------------------------------------
>
> Key: TEZ-2981
> URL: https://issues.apache.org/jira/browse/TEZ-2981
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: André Kelpe
>
> In Cascading we are sub-classing the DAGClientImpl and implementing the
> TimeLineClient interface in order to get to all the task level data. Since
> these are non-stable APIs we would like to have an API on the DAGClient to
> get to that information w/o having to talk to the TimeLineServer ourselves.
> Similar to how the APIs work over in MapReduce, where there is an API to get
> to the TaskAttempt data w/o having to know, how it is stored in the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
