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

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

[~hitesh]
Attaching a fresh patch that display the following error message.

{code}
Data is not available!
No data returned from URL: {url}. The data may not be available in YARN 
Timeline or you may not have the necessary permissions to view this data.
{code}

> 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: 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
(v6.3.4#6332)

Reply via email to