[jira] Commented: (HADOOP-3098) dfs -chown does not like "_" underscore in user name

["Raghu Angadi (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582405#action_12582405 ] 

Raghu Angadi commented on HADOOP-3098:
--------------------------------------

Sure. There was no particular reason to restrict it to alphanumberic only.  Of course we don't need to limit it to 8 characters. 

One problem is period(.) : what does 'chown raghu.user file' mean, is 'user' group name or part of the user name? On linux it will set the file onwer to raghu and group owner to user. Also these os' have advantage of being able to validate it some this a known username or not (from /etc/passwd). All we do now is to match a regex.

What about spaces?

I can propose a regex here.


> dfs -chown does not like "_" underscore in user name
> ----------------------------------------------------
>
>                 Key: HADOOP-3098
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3098
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.16.0, 0.16.1
>            Reporter: Koji Noguchi
>            Priority: Blocker
>             Fix For: 0.16.2
>
>
> :~$ 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=view
> bq. 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.