[
https://issues.apache.org/jira/browse/HDFS-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe updated HDFS-8305:
---------------------------------------
Description: HDFS INotify: the destination field of RenameOp should always
end with the file name rather than sometimes being a directory name.
Previously, in some cases when using the old rename, this was not the case.
The format of OP_EDIT_LOG_RENAME_OLD allows moving /f to /d/f to be represented
as RENAME(src=/f, dst=/d) or RENAME(src=/f, dst=/d/f). This change makes HDFS
always use the latter form. This, in turn, ensures that inotify will always be
able to consider the dst field as the full destination file name. This is a
compatible change since we aren't removing the ability to handle the first form
during edit log replay... we just no longer generate it. (was: HDFS INotify:
the destination field of RenameOp should always end with the file name rather
than sometimes being a directory name.)
> HDFS INotify: the destination field of RenameOp should always end with the
> file name
> ------------------------------------------------------------------------------------
>
> Key: HDFS-8305
> URL: https://issues.apache.org/jira/browse/HDFS-8305
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-8305.001.patch
>
>
> HDFS INotify: the destination field of RenameOp should always end with the
> file name rather than sometimes being a directory name. Previously, in some
> cases when using the old rename, this was not the case. The format of
> OP_EDIT_LOG_RENAME_OLD allows moving /f to /d/f to be represented as
> RENAME(src=/f, dst=/d) or RENAME(src=/f, dst=/d/f). This change makes HDFS
> always use the latter form. This, in turn, ensures that inotify will always
> be able to consider the dst field as the full destination file name. This is
> a compatible change since we aren't removing the ability to handle the first
> form during edit log replay... we just no longer generate it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
