[
https://issues.apache.org/jira/browse/HADOOP-11254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192906#comment-14192906
]
Hadoop QA commented on HADOOP-11254:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12678579/HADOOP-11254.1.patch
against trunk revision 1cd088f.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5000//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5000//console
This message is automatically generated.
> Promoting AccessControlList to be public
> ----------------------------------------
>
> Key: HADOOP-11254
> URL: https://issues.apache.org/jira/browse/HADOOP-11254
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Attachments: HADOOP-11254.1.patch
>
>
> The motivation of promoting AccessControlList to be a public API is to
> facilitate the users to programmatically parse or construct an ACL string. A
> typical use case may be the timeline domain, where we have the client lib to
> accept strings complied with ACL string format to define the authorized
> readers/writers. It will be more convenient and less buggy if users can
> compose this string with AccessControlList.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
