[ https://issues.apache.org/jira/browse/YARN-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112839#comment-14112839
]
Hadoop QA commented on YARN-2102:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12664732/YARN-2102.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 8 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 eclipse:eclipse.
{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:red}-1 core tests{color}. The test build failed in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-YARN-Build/4745//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4745//console
This message is automatically generated.
> More generalized timeline ACLs
> ------------------------------
>
> Key: YARN-2102
> URL: https://issues.apache.org/jira/browse/YARN-2102
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: GeneralizedTimelineACLs.pdf, YARN-2102.1.patch, YARN-2102.2.patch,
YARN-2102.3.patch, YARN-2102.5.patch
>
>
> We need to differentiate the access controls of reading and writing operations, and we
need to think about cross-entity access control. For example, if we are executing a workflow
of MR jobs, which writing the timeline data of this workflow, we don't want other user to
pollute the timeline data of the workflow by putting something under it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
|