[jira] Commented: (HADOOP-6240) Rename operation is not consistent betwee different implementations of FileSystem

["Suresh Srinivas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751566#action_12751566 ] 

Suresh Srinivas commented on HADOOP-6240:
-----------------------------------------

There are two problems to address:
# Define clearly what the behavior of rename functionality shoudl be
# Ensure all the FileSystem implementations adhere to it

Before looking at how different implementations of {{FileSystem}} in hadoop behave, lets decide on the expected behavior under different boundary conditions. Posix (http://www.opengroup.org/onlinepubs/009695399/functions/rename.html) defines the following:
# Renaming a file to a directory or directory to a file should fail.
# Renaming old file to a new file that exists should succeed. Existing new file is removed before rename.
# Renaming old dir to a new dir that exists and is not empty should fail
# Renaming old dir to a new dir that exists and is empty should succeed. Existing new dir is removed before rename.
# The new pathname that contains the old path as prefix should fail.
# Renaming to a new path with non-existent directory (rename /a/b to /c/d where c does not exist) should fail


For indicating failure in above cases, {{IOException}} will be thrown instead of returning {{false}}.



> Rename operation is not consistent betwee different implementations of FileSystem
> ---------------------------------------------------------------------------------
>
>                 Key: HADOOP-6240
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6240
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.21.0
>
>
> The rename operation has many scenarios that are not consistently implemented across file systems.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.