hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13585) shell rm command to not rename to ~/.Trash in object stores
Date Thu, 07 Sep 2017 09:24:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-13585:
------------------------------------
    Parent Issue: HADOOP-14831  (was: HADOOP-13204)

> shell rm command to not rename to ~/.Trash in object stores
> -----------------------------------------------------------
>
>                 Key: HADOOP-13585
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13585
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: util
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>
> When you do a {{hadoop fs -rm -s3a://bucket/large-file}} there's a long delay and then
you are told that it's been moved to {{s3a://Users/stevel/.Trash/current/large-file}}. Where
it still incurs costs. You need to then delete that file using {{-skipTrash}} because the
{{fs -expunge}} command only works on the local fs: you can't point it at an object store
unless that is the default FS.
> I'd like an option to tell the shell to tell it that it should bypass the renaming on
an FS-by-FS basis. And the for {{fs expunge}} to take a filesystem as an optional argument.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message