[
https://issues.apache.org/jira/browse/HADOOP-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-3098:
---------------------------------
Attachment: HADOOP-3098.patch
Updated the patch to allow '@' and '/'. Documentation includes an explicit warning for Linux users (may be 90+% of hadoop users?) :
{noformat}
$ bin/hadoop fs -Dfs.default.name=file:/// -help chown
-chown [-R] [OWNER][:[GROUP]] PATH...
Changes owner and group of a file.
This is similar to shell's chown with a few exceptions.
-R modifies the files recursively. This is the only option
currently supported.
If only owner or group is specified then only owner or
group is modified.
The owner and group names may only cosists of digits, alphabet,
and any of '-_.@/' i.e. [-_.@/a-zA-Z0-9]. The names are case
sensitive.
WARNING: Avoid using '.' to separate user name and group though
Linux allows it. If user names have dots in them and you are
using local file system, you might see surprising results since
shell command 'chown' is used for local files.
{noformat}
dfs -chown does not like "_" underscore in user name
----------------------------------------------------
Key: HADOOP-3098
URL:
https://issues.apache.org/jira/browse/HADOOP-3098Project: Hadoop Core
Issue Type: Bug
Components: fs
Affects Versions: 0.16.0, 0.16.1
Reporter: Koji Noguchi
Assignee: Raghu Angadi
Priority: Blocker
Fix For: 0.16.2
Attachments: HADOOP-3098.patch, HADOOP-3098.patch
:~$ hadoop dfs -chown aaa_bbb /user/knoguchi/test.txt
chown: 'aaa_bbb' does not match expected pattern for [owner][:group].
in 0.16.1, only alphabets and numbers are allowed. Shouldn't '_' be allowed?
I couldn't find any standard, but in Solaris10, it's defined as
http://docs.sun.com/app/docs/doc/816-5174/6mbb98uhg?a=viewbq. The login (login) and role (role) fields accept a string of no more than eight bytes consisting of characters from the set of alphabetic characters, numeric characters, period (.), underscore (_), and hyphen (-). The first character should be alphabetic and the field should contain at least one lower case alphabetic character. A warning message is displayed if these restrictions are not met.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.