[
https://issues.apache.org/jira/browse/HADOOP-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056626#comment-14056626
]
jay vyas commented on HADOOP-10779:
-----------------------------------
agreed: The most important thing is to
1) Update the definition of the supergroup in the xml file to clarify what
you've said here.
2) find examples where the ecosystem tools are using the supergroup and
determine if its being used in the idiomatic way.
So the conclusion to this JIRA could be a simple patch to the hdfs-site.xml
improves the description of the dfs.permissions.supergroup.key parameter and
what the hdfs supergroup is meant to be used for.
> 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: fs
> Reporter: Martin Bukatovic
> Priority: Minor
>
> 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.2#6252)
