[ 
https://issues.apache.org/jira/browse/TEZ-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sreenath Somarajapuram updated TEZ-2915:
----------------------------------------
    Description: 
On clicking breadcrumb, go to the details page than the tables.

An example while tracking a running DAG.
1. Go to the DAG page. (Shows the progress table).
2. Click on a specific vertex - goes to the vertex table.
3. Click the DAG link on the top left of the page. Expecting this to go back to 
the DAG page, Instead it goes to the All Vertices page - which has similar 
information to the All DAG page, but no task level info.
Getting back to the DAG progress page is difficult

  was:
An example while tracking a running DAG.
1. Go to the DAG page. (Shows the progress table).
2. Click on a specific vertex - goes to the vertex table.
3. Click the DAG link on the top left of the page. Expecting this to go back to 
the DAG page, Instead it goes to the All Vertices page - which has similar 
information to the All DAG page, but no task level info.
Getting back to the DAG progress page is difficult


> Tez UI: Getting back to the DAG details page is difficult
> ---------------------------------------------------------
>
>                 Key: TEZ-2915
>                 URL: https://issues.apache.org/jira/browse/TEZ-2915
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>             Fix For: 0.7.1, 0.8.2
>
>
> On clicking breadcrumb, go to the details page than the tables.
> An example while tracking a running DAG.
> 1. Go to the DAG page. (Shows the progress table).
> 2. Click on a specific vertex - goes to the vertex table.
> 3. Click the DAG link on the top left of the page. Expecting this to go back 
> to the DAG page, Instead it goes to the All Vertices page - which has similar 
> information to the All DAG page, but no task level info.
> Getting back to the DAG progress page is difficult



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to