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 "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2010/03/22 22:09:27 UTC
[jira] Created: (HADOOP-6655) SLA related changes in
hadoop-policy.xml have misleading property descriptions
SLA related changes in hadoop-policy.xml have misleading property descriptions
------------------------------------------------------------------------------
Key: HADOOP-6655
URL: https://issues.apache.org/jira/browse/HADOOP-6655
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.20.2
Reporter: Konstantin Boudnik
In the patch introduced my HADOOP-4348 proposed modifications of {{hadoop-policy.xml}} read on more than one occasion:
{noformat}
+ The ACL is a comma-separated list of user and group names. The user and
+ group list is separated by a blank. For e.g. "alice,bob users,wheel".
{noformat}
It is either should read "separated by a semicolon" or the given example has to be changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6655) SLA related changes in
hadoop-policy.xml have misleading property descriptions
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848756#action_12848756 ]
Vinod K V commented on HADOOP-6655:
-----------------------------------
Kos, the ACL proposed in HADOOP-4348 actually used a space character as the user-group list separator. The same AccessControlList is used for other features like queue administration and I know of code throughout MapReduce that hardcodes this same assumption for the lack of good API to deconstruct an ACL or modify an already constructed ACL.
Are you proposing we change the character separator to a semi-coloon? Any reason for this? Now?
> SLA related changes in hadoop-policy.xml have misleading property descriptions
> ------------------------------------------------------------------------------
>
> Key: HADOOP-6655
> URL: https://issues.apache.org/jira/browse/HADOOP-6655
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.20.2
> Reporter: Konstantin Boudnik
>
> In the patch introduced my HADOOP-4348 proposed modifications of {{hadoop-policy.xml}} read on more than one occasion:
> {noformat}
> + The ACL is a comma-separated list of user and group names. The user and
> + group list is separated by a blank. For e.g. "alice,bob users,wheel".
> {noformat}
> It is either should read "separated by a semicolon" or the given example has to be changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-6655) SLA related changes in
hadoop-policy.xml have misleading property descriptions
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik resolved HADOOP-6655.
----------------------------------------
Resolution: Invalid
I'm proposing to close this JIRA because I've misread the test in the config file. Nevermind.
> SLA related changes in hadoop-policy.xml have misleading property descriptions
> ------------------------------------------------------------------------------
>
> Key: HADOOP-6655
> URL: https://issues.apache.org/jira/browse/HADOOP-6655
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 0.20.2
> Reporter: Konstantin Boudnik
>
> In the patch introduced my HADOOP-4348 proposed modifications of {{hadoop-policy.xml}} read on more than one occasion:
> {noformat}
> + The ACL is a comma-separated list of user and group names. The user and
> + group list is separated by a blank. For e.g. "alice,bob users,wheel".
> {noformat}
> It is either should read "separated by a semicolon" or the given example has to be changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.