Hadoop QA commented on YARN-3267:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 863079b.

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

    {color:green}+1 tests included{color}.  The patch appears to include 6 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 eclipse:eclipse{color}.  The patch built with 

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) 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-YARN-Build/6947//console

This message is automatically generated.

> Timelineserver applies the ACL rules after applying the limit on the number 
> of records
> --------------------------------------------------------------------------------------
>                 Key: YARN-3267
>                 URL: https://issues.apache.org/jira/browse/YARN-3267
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Prakash Ramachandran
>            Assignee: Chang Li
>         Attachments: YARN-3267.3.patch, YARN-3267.4.patch, YARN-3267.5.patch, 
> YARN_3267_V1.patch, YARN_3267_V2.patch, YARN_3267_WIP.patch, 
> YARN_3267_WIP1.patch, YARN_3267_WIP2.patch, YARN_3267_WIP3.patch
> While fetching the entities from timelineserver, the limit is applied on the 
> entities to be fetched from leveldb, the ACL filters are applied after this 
> (TimelineDataManager.java::getEntities). 
> this could mean that even if there are entities available which match the 
> query criteria, we could end up not getting any results.

This message was sent by Atlassian JIRA

Reply via email to