[
https://issues.apache.org/jira/browse/HADOOP-14455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080086#comment-16080086
]
Vinayakumar B commented on HADOOP-14455:
----------------------------------------
Thanks for reporting and posting patch [~brahmareddy]
There were no historic reasons mentioned or found to allow only one of the
alternative mentioned in comments. In ViewFileSystem#rename(..)
Changing the current behavior straightaway is not correct.
So it would be better to have a configuration, to keep current behavior intact
and use the configuration to have desired behavior.
There are 3 rename strategies available as of now.
1. SAME_FILESYSTEM_ACROSS_MOUNTPOINT
2. SAME_TARGET_URI_ACROSS_MOUNTPOINT
3. SAME_MOUNTPOINT
So, a config can be introduced to choose any one among the above, Default
should be SAME_MOUNTPOINT.
Based on the configuration, validation could vary.
> ViewFileSystem#rename should support be supported within same nameservice
> with different mountpoints
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-14455
> URL: https://issues.apache.org/jira/browse/HADOOP-14455
> Project: Hadoop Common
> Issue Type: Improvement
> Components: viewfs
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Attachments: HADOOP-14455-002.patch, HADOOP-14455.patch
>
>
> *Scenario:*
> || Mount Point || NameService|| Value||
> |/tmp|hacluster|/tmp|
> |/user|hacluster|/user|
> Move file from {{/tmp}} to {{/user}}
> It will fail by throwing the following error
> {noformat}
> Caused by: java.io.IOException: Renames across Mount points not supported
> at
> org.apache.hadoop.fs.viewfs.ViewFileSystem.rename(ViewFileSystem.java:500)
> at org.apache.hadoop.hive.ql.metadata.Hive.moveFile(Hive.java:2692)
> ... 22 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
