[
https://issues.apache.org/jira/browse/HDFS-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930830#comment-16930830
]
CR Hota commented on HDFS-14431:
--------------------------------
[~elgoiri] Many thanks for all the work done so far.
Took a look at the patch and approach seems error prone as the operations in
totality are NOT atomic. Filesystems are not transactional in nature.
Since rename is very hard to get right, may I suggest we approach it as we did
with some other features. Let's come up with a design doc and write down the
issues, possible approaches and what all use cases we can solve and can't. We
can all collaborate. Please count me in.
For someone new, its very hard to get the context of what is being solved and
what use cases are not.
On a side note, with the lack of atomic renames here is how we are approaching
renames in the short term. Most query engines (ex Hive) are equipped to handle
rename failure by initiating a copy. In the scenario where rename is across
clusters, hive is instructed to invoke a copy operation.
FYI [~ayushtkn] [~xuzq_zander]
> RBF: Rename with multiple subclusters should fail if no eligible locations
> --------------------------------------------------------------------------
>
> Key: HDFS-14431
> URL: https://issues.apache.org/jira/browse/HDFS-14431
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Major
> Attachments: HDFS-14431-HDFS-13891.001.patch,
> HDFS-14431-HDFS-13891.002.patch, HDFS-14431-HDFS-13891.003.patch,
> HDFS-14431-HDFS-13891.004.patch, HDFS-14431-HDFS-13891.005.patch,
> HDFS-14431-HDFS-13891.006.patch, HDFS-14431-HDFS-13891.007.patch
>
>
> Currently, the rename will fail with FileNotFoundException which is not clear
> to the user.
> The operation should fail stating the reason is that there are no eligible
> destinations.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
