Sreenath Somarajapuram updated TEZ-3419:
    Attachment: TEZ-3419.6.patch

Thanks [~hitesh]
bq. 2 screenshots show spurious data being shown in the UI.
Attaching a fresh patch with the correction. 

bq. 3rd screenshot is for the configs. Configs are not accessible due to 
permission issues but UI says no records found. I think this is a reasonable 
approach for now ( as compared to an error message indicating no data or 
permission issue ) but just wanted to make sure that this was the intention of 
the patch and not an accidental change.
Thats true. The behavior is as expected. As of now, we are just bypassing a 
failure condition.

> 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, Screen Shot 
> 2016-10-13 at 4.37.09 PM.png, Screen Shot 2016-10-17 at 4.11.29 PM.png, 
> Screen Shot 2016-10-17 at 4.11.59 PM.png, Screen Shot 2016-10-17 at 4.12.23 
> PM.png, TEZ-3419.1.patch, TEZ-3419.2.patch, TEZ-3419.3.patch, 
> TEZ-3419.4.patch, TEZ-3419.5.patch, TEZ-3419.6.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