You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/09/14 13:49:20 UTC
[jira] [Created] (HADOOP-13611) FileSystem/s3a processDeleteOnExit
to skip the exists() check
Steve Loughran created HADOOP-13611:
---------------------------------------
Summary: FileSystem/s3a processDeleteOnExit to skip the exists() check
Key: HADOOP-13611
URL: https://issues.apache.org/jira/browse/HADOOP-13611
Project: Hadoop Common
Issue Type: Sub-task
Components: fs, fs/s3
Affects Versions: 2.7.3
Reporter: Steve Loughran
Priority: Minor
If you look at {{FileSystem.processDeleteOnExit()}}, it does an exists() check for each entry, before calling delete().
That exists() check is superfluous; on s3 it add an extra 1-4 HTTP GETs
This could be fixed with a subclass in s3a to avoid it, but as the call is superfluous in *all* filesystems, it could be removed in {{FileSystem}} and so picked up by all object stores.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org