Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.8.0
-
None
-
None
Description
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
Attachments
Issue Links
- duplicates
-
HADOOP-11452 Make FileSystem.rename(path, path, options) public, specified, tested
-
- Patch Available
-
- is related to
-
HADOOP-13846 S3A to implement rename(final Path src, final Path dst, final Rename... options)
-
- Open
-
- relates to
-
HADOOP-6240 Rename operation is not consistent between different implementations of FileSystem
-
- Closed
-