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 "Mingliang Liu (JIRA)" <ji...@apache.org> on 2016/12/02 19:34:58 UTC
[jira] [Updated] (HADOOP-13856) FileSystem.rename(final Path src,
final Path dst, final Rename... options) to become public; specified,
tested
[ https://issues.apache.org/jira/browse/HADOOP-13856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu updated HADOOP-13856:
-----------------------------------
Target Version/s: 2.8.0, 3.0.0-alpha2
Component/s: (was: fs/s3)
fs
+1 for the proposal.
I set the components as "fs" and target versions "2.8.0+". Correct me if I'm wrong.
> FileSystem.rename(final Path src, final Path dst, final Rename... options) to become public; specified, tested
> --------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13856
> URL: https://issues.apache.org/jira/browse/HADOOP-13856
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
>
> A lot of code within Hadoop (e.g. committers, filesystem) and downstream (Hive, spark), don't know what to do when rename() returns false, as it can be a sign of nothing important, or something major.
> In contrast, {{rename(final Path src, final Path dst, final Rename... options)}} has stricter semantics and throws up all exceptions to be caught or relayed by callers. Yet it cannot be used as its scoped at {{protected}} and tagged as {{@Deprected}}.
> If it was made public then it could be used in committers and elsewhere; if we backport the making of it public, then life will be even better
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org