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 "Steve Loughran (Jira)" <ji...@apache.org> on 2025/01/15 17:39:00 UTC

[jira] [Resolved] (HADOOP-13846) S3A to implement rename(final Path src, final Path dst, final Rename... options)

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

Steve Loughran resolved HADOOP-13846.
-------------------------------------
    Release Note: 
I've played with this in the path and am just going to give up.

rename is not how things should be working with s3 data
      Resolution: Fixed

> S3A to implement rename(final Path src, final Path dst, final Rename... options)
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-13846
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13846
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Priority: Major
>
> S3a now raises exceptions on invalid rename operations, but these get lost. I plan to use them in my s3guard committer HADOOP-13786.
> Rather than just make innerRename() private, S3A could implement {{FileSystem.rename(final Path src, final Path dst, final Rename... options)}} and so have an exception-raising rename which can be called without going more into the internals. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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