You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Chang Li (JIRA)" <ji...@apache.org> on 2015/02/27 22:27:05 UTC
[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules
after applying the limit on the number of records
[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340837#comment-14340837 ]
Chang Li commented on YARN-3267:
--------------------------------
[~pramachandran] Could you take a look at my solution in my wip patch, I tried to solve this problem by pass a functor into the getEntities()call in TimelineReader, and inside LeveldbTimelineStore I check acl before add each entity.
Also I am about to write a unit test, where should I put this unit test?
Thanks
> 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_WIP.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
(v6.3.4#6332)