TezQA commented on TEZ-3419:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against master revision 48208dc.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:green}+1 tests included{color}.  The patch appears to include 5 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2041//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: Screen Shot 2016-10-13 at 4.25.31 PM.png, Screen Shot 
> 2016-10-13 at 4.37.09 PM.png, TEZ-3419.1.patch, TEZ-3419.2.patch, 
> TEZ-3419.3.patch, TEZ-3419.4.patch, TEZ-3419.5.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