[
https://issues.apache.org/jira/browse/HDFS-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843102#comment-16843102
]
Ayush Saxena commented on HDFS-14431:
-------------------------------------
Thanx [~elgoiri] for the update. Didn't check the entire code, I need to go
through it again.
bq.HASH needs to have the folders in all subclusters if we need to rename a
file. Changed DestinationOrder.
Do you intend to change the behavior of HASH order? If so, probably we
shouldn't.
bq. When renaming with OVERWRITE, we may need to delete the file from another
subcluster. This is done in RenameParam#getLocationsToDelete().
Can you explain a bit more, cross cluster rename is not possible I guess. Which
scenario it comes in.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
