You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/07/31 18:59:20 UTC
[jira] [Updated] (TEZ-3389) [Umbrella] Imrove DAG Client/Reporting
functionality
[ https://issues.apache.org/jira/browse/TEZ-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hitesh Shah updated TEZ-3389:
-----------------------------
Issue Type: New Feature (was: Bug)
> [Umbrella] Imrove DAG Client/Reporting functionality
> ----------------------------------------------------
>
> Key: TEZ-3389
> URL: https://issues.apache.org/jira/browse/TEZ-3389
> Project: Apache Tez
> Issue Type: New Feature
> Reporter: Hitesh Shah
>
> This umbrella jira will cover the various improvements and fixes needed in the client-side layer:
> - Improve the DAGClient APIs to provide access to basic dag plan info ( vertex dependencies, name-to-id mapping, etc)
> - Enhance DAGClient to provide access to task level information similar to MR
> - Allow the DAGClient to be constructed separately outside of the TezClient/Session.
> - Create a CLI which can provide basic reporting/status progress updates functionality for sessions and DAGs.
> - Ensure that the CLI can function against different versions of Tez. i.e. in case of upgrades, there may be a scenario where an older CLI tries to communicate with a newer Tez AM or reads data from ATS where the data was written by a newer version. For a newer CLI, it should be able to fully read older data sets. For an older CLI, it should degrade gracefully whenever possible or error out with a clear message if it cannot handle the data/rpc.
> - Newer Tez AMs should be able to support requests coming in from older client versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)