[
https://issues.apache.org/jira/browse/HADOOP-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486234#comment-13486234
]
Allen Wittenauer commented on HADOOP-8456:
------------------------------------------
bq. Generally, we want to natively integrate Hadoop with Windows, in a sense
that Windows user/group information flows thru Hadoop.
bq. Let me know if this makes sense.
It does, but I'm just trying to get a measure for what the user
expectation/experience is going to be for those that are going to use this
interface. (Which, I suspect, is what Daryn's questions are about as well).
'ls' is a UNIXy thing, which why I asked specifically about cygwin and SUA. If
Windows users are expecting different output, it may be worthwhile to implement
a dir subcommand.
In other words, we should implement 'expected behavior' not necessarily what is
convenient if there is a collision. (But convenience can always be provided via
an option...) So if cygwin/sua show with spaces by default, that's what we
should do. If they provide an option that puts separators in place, that's
what we should. Consistency is key for (inter)operability.
> Support spaces in user names and group names in results returned via winutils
> -----------------------------------------------------------------------------
>
> Key: HADOOP-8456
> URL: https://issues.apache.org/jira/browse/HADOOP-8456
> Project: Hadoop Common
> Issue Type: Bug
> Components: native
> Affects Versions: 1-win
> Reporter: Chuan Liu
> Assignee: Ivan Mitic
> Priority: Minor
> Attachments: HADOOP-8456.branch-1-win.spaces.patch
>
>
> When parsing results returned by ‘ls’, we made implicit assumption that user
> and group names cannot contain spaces. On Linux, spaces are not allowed in
> user names and group names. This is not the case for Windows. We need to find
> a way to fix the problem for Windows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
