hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8305) HDFS INotify: the destination field of RenameOp should always end with the file name
Date Tue, 05 May 2015 18:08:01 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colin Patrick McCabe updated HDFS-8305:
---------------------------------------
          Resolution: Fixed
       Fix Version/s: 2.7.1
    Target Version/s: 2.7.1  (was: 2.8.0)
              Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 2.7.1
>
>         Attachments: HDFS-8305.001.patch, HDFS-8305.002.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)

Mime
View raw message