[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Bokor updated HDFS-6262:
---
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
Closing this as "Won't Fix". Please check the [related
comment|https://issues.apache.org/jira/browse/HDFS-303?focusedCommentId=15677026=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15677026].
> HDFS doesn't raise FileNotFoundException if the source of a rename() is
> missing
> ---
>
> Key: HDFS-6262
> URL: https://issues.apache.org/jira/browse/HDFS-6262
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.4.0
>Reporter: Steve Loughran
>Assignee: Akira Ajisaka
> Labels: BB2015-05-TBR
> Attachments: HDFS-6262.2.patch, HDFS-6262.patch
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HDFS-6262:
---
Labels: BB2015-05-TBR (was: )
HDFS doesn't raise FileNotFoundException if the source of a rename() is
missing
---
Key: HDFS-6262
URL: https://issues.apache.org/jira/browse/HDFS-6262
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.4.0
Reporter: Steve Loughran
Assignee: Akira AJISAKA
Labels: BB2015-05-TBR
Attachments: HDFS-6262.2.patch, HDFS-6262.patch
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated HDFS-6262:
Release Note: HDFS's rename(src, dst) throws FileNotFoundException instead
of returning false if the source of the rename does not exist.
Hadoop Flags: Incompatible change
HDFS doesn't raise FileNotFoundException if the source of a rename() is
missing
---
Key: HDFS-6262
URL: https://issues.apache.org/jira/browse/HDFS-6262
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.4.0
Reporter: Steve Loughran
Assignee: Akira AJISAKA
Attachments: HDFS-6262.patch
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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated HDFS-6262:
Attachment: HDFS-6262.2.patch
HDFS doesn't raise FileNotFoundException if the source of a rename() is
missing
---
Key: HDFS-6262
URL: https://issues.apache.org/jira/browse/HDFS-6262
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.4.0
Reporter: Steve Loughran
Assignee: Akira AJISAKA
Attachments: HDFS-6262.2.patch, HDFS-6262.patch
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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated HDFS-6262:
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. (was: HDFS's rename(src, dst) throws FileNotFoundException instead
of returning false if the source of the rename does not exist.)
HDFS doesn't raise FileNotFoundException if the source of a rename() is
missing
---
Key: HDFS-6262
URL: https://issues.apache.org/jira/browse/HDFS-6262
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.4.0
Reporter: Steve Loughran
Assignee: Akira AJISAKA
Attachments: HDFS-6262.2.patch, HDFS-6262.patch
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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated HDFS-6262:
Attachment: HDFS-6262.patch
Attaching an initial patch.
HDFS doesn't raise FileNotFoundException if the source of a rename() is
missing
---
Key: HDFS-6262
URL: https://issues.apache.org/jira/browse/HDFS-6262
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.4.0
Reporter: Steve Loughran
Assignee: Akira AJISAKA
Attachments: HDFS-6262.patch
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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HDFS-6262) HDFS doesn't raise FileNotFoundException if the source of a rename() is missing
[
https://issues.apache.org/jira/browse/HDFS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA updated HDFS-6262:
Status: Patch Available (was: Open)
HDFS doesn't raise FileNotFoundException if the source of a rename() is
missing
---
Key: HDFS-6262
URL: https://issues.apache.org/jira/browse/HDFS-6262
Project: Hadoop HDFS
Issue Type: Bug
Components: namenode
Affects Versions: 2.4.0
Reporter: Steve Loughran
Assignee: Akira AJISAKA
Attachments: HDFS-6262.patch
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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
