You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Sreenath Somarajapuram (JIRA)" <ji...@apache.org> on 2017/04/19 15:12:41 UTC
[jira] [Updated] (TEZ-3631) Tez UI: TEZ_DAG_EXTRA_INFO
compatibility changes - Makes All DAGs page faster.
[ https://issues.apache.org/jira/browse/TEZ-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreenath Somarajapuram updated TEZ-3631:
----------------------------------------
Description:
TEZ-3611 will be moving dagPlan and counters into a new entity of type TEZ_DAG_EXTRA_INFO. Thus TEZ_DAG_ID entity would be lighter and would load faster.
This ticket is to ensure that the UI works as expected with the new changes and is backward compatible.
Need to consider the following cases:
1. TEZ_DAG_EXTRA_INFO must be loaded only from the inner pages and not in All DAGs page
2. Add TEZ_DAG_EXTRA_INFO must be part of Dag data zip
3. Caller Contex should be taken from the DAG JSON and not from DAG Plan
4. Display a button in All DAGs table for the user to load counter data if required. Display a tooltip saying that this operation would be costly.
5. Maintain backward compatibility
was:
TEZ-3611 will be moving dagPlan and counters into a new entity of type TEZ_DAG_EXTRA_INFO. Thus TEZ_DAG_ID entity would be lighter and would load faster.
This ticket is to ensure that the UI works as expected with the new changes and is backward compatible.
> Tez UI: TEZ_DAG_EXTRA_INFO compatibility changes - Makes All DAGs page faster.
> ------------------------------------------------------------------------------
>
> Key: TEZ-3631
> URL: https://issues.apache.org/jira/browse/TEZ-3631
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
>
> TEZ-3611 will be moving dagPlan and counters into a new entity of type TEZ_DAG_EXTRA_INFO. Thus TEZ_DAG_ID entity would be lighter and would load faster.
> This ticket is to ensure that the UI works as expected with the new changes and is backward compatible.
> Need to consider the following cases:
> 1. TEZ_DAG_EXTRA_INFO must be loaded only from the inner pages and not in All DAGs page
> 2. Add TEZ_DAG_EXTRA_INFO must be part of Dag data zip
> 3. Caller Contex should be taken from the DAG JSON and not from DAG Plan
> 4. Display a button in All DAGs table for the user to load counter data if required. Display a tooltip saying that this operation would be costly.
> 5. Maintain backward compatibility
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)