You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2014/10/31 19:37:34 UTC

[jira] [Commented] (HADOOP-11254) Promoting AccessControlList to be public

    [ https://issues.apache.org/jira/browse/HADOOP-11254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192225#comment-14192225 ] 

Hitesh Shah commented on HADOOP-11254:
--------------------------------------

[~zjshen] Thanks for filing the issue. The context/use-case for this came about when looking at trying to integrate Tez with Timeline for ACLs. Given that Timeline today does not support incremental updates to ACLs, to update ACLs one needs to parse the original ACL string and update it with additional users/groups. The AccessControlList class being made public would be very useful for this. 

> 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
>
> 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)