[HDFS-6262] HDFS doesn't raise FileNotFoundException if the source of a rename() is missing

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.4.0
• Component/s: namenode
• Labels: BB2015-05-TBR
• Hadoop Flags: Incompatible change
• Release Note: HDFS's rename(src, dst) throws FileNotFoundException instead of logging warn message and returning false if the source of the rename does not exist.
• Assignee: Akira Ajisaka
• Reporter: Steve Loughran
• Created: 20/Apr/14 20:54
• Updated: 30/Nov/16 11:47
• Resolved: 29/Nov/16 17:04

Description

HDFS's rename(src, dest) returns false if src does not exist -all the other filesystems raise FileNotFoundException

This behaviour is defined in FSDirectory.unprotectedRenameTo() -the attempt is logged, but the operation then just returns false.

I propose changing the behaviour of DistributedFileSystem to be the same as that of the others -and of FileContext, which does reject renames with nonexistent sources

Issue Links

• is part of: HDFS-303 Make contracts of LocalFileSystem and DistributedFileSystem consistent
• relates to: HADOOP-6240 Rename operation is not consistent between different implementations of FileSystem
• relates to: HDFS-654 HDFS needs to support new rename introduced for FileContext