[
https://issues.apache.org/jira/browse/HDFS-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247748#comment-13247748
]
Colin Patrick McCabe commented on HDFS-3206:
--------------------------------------------
Hi Bikras,
The edit log reflects changes to the image, not the contents of the image
themselves. It's a series of deltas. So it is quite possible to have an
OP_SET_OWNER that contains no user name, despite the fact that all files have
an owning user associated with them. It just means that at some point, someone
changed the group in which the file resides, without changing the owner at the
same time.
> 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
