[ https://issues.apache.org/jira/browse/TEZ-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530961#comment-15530961 ]
TezQA commented on TEZ-3419: ---------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12830788/YARN%20%26%20Tez%20data%20missing.png against master revision 5c2f893. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1992//console This message is automatically generated. > 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.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)