[
https://issues.apache.org/jira/browse/HDFS-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247544#comment-13247544
]
Bikas Saha commented on HDFS-3206:
----------------------------------
At a higher level, is it ok for no user owner to exist and only have a group
owner?
The current XML code seems to imply that a user will always be there. If that
is true, and this bug showed up then it implies some namenode code is broken
because it allows ownership to be group only.
Aside from that, the XML serde code should not reflect namenode behavior. So
the fix looks good.
> oev: miscellaneous xml cleanups
> -------------------------------
>
> Key: HDFS-3206
> URL: https://issues.apache.org/jira/browse/HDFS-3206
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HDFS-3206.001.patch
>
>
> * SetOwner operations can change both the user and group which a file or
> directory belongs to, or just one of those. Currently, in the XML
> serialization/deserialization code, we don't handle the case where just the
> group is set, not the user. We should handle this case.
> * consistently serialize generation stamp as GENSTAMP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
