[
https://issues.apache.org/jira/browse/TEZ-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4279:
------------------------------
Description:
Currently, Hiveserver2 cannot be sure about dag some details (e.g. vertex ids),
and there is a chance that by using e.g. vertex ids, some specific logic might
be run after dag completion.
was:The proposal is: similar to StatusGetOpts.GET_COUNTERS,
StatusGetOpts.GET_DAG_DETAILS could be sent to the AM if the client needs
details about the vertices for instance. Currently, Hiveserver2 cannot be sure
about dag details (e.g. vertex ids), and there is a chance that by using e.g.
vertex ids, some specific logic might be run after dag completion. Tez is not
supposed to be aware of those actions, only supposed to provide an extensible
dag data by the dag client for upstream applications.
> Support some dag/vertex details in DagClient
> --------------------------------------------
>
> Key: TEZ-4279
> URL: https://issues.apache.org/jira/browse/TEZ-4279
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
>
> Currently, Hiveserver2 cannot be sure about dag some details (e.g. vertex
> ids), and there is a chance that by using e.g. vertex ids, some specific
> logic might be run after dag completion.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
