[
https://issues.apache.org/jira/browse/HADOOP-13846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706366#comment-15706366
]
Steve Loughran commented on HADOOP-13846:
-----------------------------------------
Requirements
# rename/3 behaviour to be specified fully. It's better than rename/2 here.
# contract tests
# S3a to implement with contract tests
# have rename/2 forward to the new rename, catching IOEs and downgrading to
return codes, the way it now does. Are behaviours consistent enough to do that?
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
