hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Bukatovic (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10779) Generalize DFS_PERMISSIONS_SUPERUSERGROUP_KEY for any HCFS
Date Fri, 28 Nov 2014 14:55:12 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Bukatovic updated HADOOP-10779:
--------------------------------------
    Labels: hcfs  (was: )

> Generalize DFS_PERMISSIONS_SUPERUSERGROUP_KEY for any HCFS
> ----------------------------------------------------------
>
>                 Key: HADOOP-10779
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10779
>             Project: Hadoop Common
>          Issue Type: Wish
>          Components: documentation, fs
>            Reporter: Martin Bukatovic
>            Priority: Minor
>              Labels: hcfs
>
> HDFS has configuration option {{dfs.permissions.superusergroup}} stored in
> {{hdfs-site.xml}} configuration file:
> {noformat}
> <property>
>   <name>dfs.permissions.superusergroup</name>
>   <value>supergroup</value>
>   <description>The name of the group of super-users.</description>
> </property>
> {noformat}
> Since we have an option to use alternative Hadoop filesystems (HCFS), there is
> a question how to specify a supergroup in such case.
> Eg. would introducing HCFS option in say {{core-site.xml}} for this as shown
> below make sense?
> {noformat}
> <property>
>   <name>hcfs.permissions.superusergroup</name>
>   <value>${dfs.permissions.superusergroup}</value>
>   <description>The name of the group of super-users.</description>
> </property>
> {noformat}
> Or would you solve it in different way? I would like to at least declare 
> a recommended approach for alternative Hadoop filesystems to follow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message