Hitesh Shah updated TEZ-3419:
    Attachment: Screen Shot 2016-10-13 at 4.25.31 PM.png

[~Sreenath] Most of the functionality seems to look fine but I am not sure I 
understand what a user will assume when faced with the error seen in the 
screenshot. This is on a setup where the tez app data cannot be obtained from 
timeline due to no permissions ( but YARN RM is not enforcing acls in this 
setup so data does come back from the RM ) and the DAG data has acls to allow 
the viewer to see dags. 

> Tez UI: Applications page shows error, for users with only DAG level ACL 
> permission.
> ------------------------------------------------------------------------------------
>                 Key: TEZ-3419
>                 URL: https://issues.apache.org/jira/browse/TEZ-3419
>             Project: Apache Tez
>          Issue Type: Sub-task
>    Affects Versions: 0.7.0
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: Screen Shot 2016-10-13 at 4.25.31 PM.png, 
> TEZ-3419.1.patch, TEZ-3419.2.patch, TEZ-3419.3.patch, TEZ-3419.4.patch, 
> TEZ-3419.wip.1.patch, Tez data missing.png, YARN & Tez data missing.png, YARN 
> data missing.png
> Follow this logic and display better message:
> On loading app details page, send a request to 
> <ats-address>/ws/v1/timeline/TEZ_APPLICATION/tez_<app-id>
> - If it succeed, display the details page as we do now.
> - If it fails, send a request to 
> <ats-address>/ws/v1/timeline/TEZ_DAG_ID?primaryFilter=applicationId%3A<app-id>
> -- If it succeed, then we know that DAGs under the app are available and 
> assume that the user doesn't have permission to access app level data.
> --- If AHS is accessible, display application data from there in the details 
> page.
> --- else if AHS is not accessible, display a message in app details tab, 
> something like "Data is not available. Check if you are authorized to access 
> application data!".
> --- Also display the DAGs tab, for the user to see DAGs under that app.
> -- If it fails, display error message as we do now.

This message was sent by Atlassian JIRA

Reply via email to