[
https://issues.apache.org/jira/browse/HADOOP-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055633#comment-14055633
]
jay vyas commented on HADOOP-10779:
-----------------------------------
I agree that at least a best practice should be defined, maybe [~cmccabe] is
right - but at first glance I think I only half heartedly agree with his
argument :). Here is why:
I don't think the actual value of defining a *supergroup* is predicated on the
way that you *become* the supergroup. Rather, its in the semantics of how the
supergroup concept is used in the broader ecosystem. In hadoop, the
*supergroup* is used to determine which users should be allowed to do certain
operations. From a hadoop interoperability and compatibility perspective,
surely the idea that certain groups of people have privileged abilities in a
file system is generic, wouldn't you say ?
Maybe the next step is to find 3 or 4 examples of how the hadoop ecosystem is
using the dfs.permissions.supergroup parameter... Either (1) they are only
using it in HDFS specific context or (2) they are using it for broader
semantics. Maybe, to colin's idea, its possible that some are misusing the
parameter to mean *more * than it actually is meant to mean, in which case
individual bugs be filed where those instances are found.
> 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)
