You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Daryn Sharp (JIRA)" <ji...@apache.org> on 2012/07/27 23:12:34 UTC
[jira] [Updated] (HADOOP-8627) FS deleteOnExit may delete the wrong
path
[ https://issues.apache.org/jira/browse/HADOOP-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daryn Sharp updated HADOOP-8627:
--------------------------------
Status: Patch Available (was: Open)
> FS deleteOnExit may delete the wrong path
> -----------------------------------------
>
> Key: HADOOP-8627
> URL: https://issues.apache.org/jira/browse/HADOOP-8627
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.0-alpha, 0.23.0, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-8627.patch
>
>
> {{FilterFileSystem}} is incorrectly delegating {{deleteOnExit}} to the raw underlying fs. This is wrong, because each fs instance is intended to maintain its own pool of temp files. Worse yet, this means registering a file via {{ChRootedFileSystem#deleteOnExit}} will delete the file w/o the chroot path prepended!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira