[jira] [Commented] (HDFS-16487) RBF: getListing uses raw mount table points

["Fengnan Li (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498302#comment-17498302 ] 

Fengnan Li commented on HDFS-16487:
-----------------------------------

[~elgoiri] What is the intention of the original design to include raw mounts? Are there use cases dependent on this behavior?

> RBF: getListing uses raw mount table points
> -------------------------------------------
>
>                 Key: HDFS-16487
>                 URL: https://issues.apache.org/jira/browse/HDFS-16487
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Fengnan Li
>            Assignee: Fengnan Li
>            Priority: Major
>
> In getListing, the result is a union of subclusters results and mount points. However these two are of different concepts and the latter one is something Router internal. It is very possible that the actual path doesn't exist in the dest HDFS yet. 
> Can we choose a different strategy that check each children mount point and confirm there is the HDFS path in the dest cluster? If so, we can add it; otherwise we should skip this mount because it confuses clients. (Clients could directly create a subdir under a dangling mount point)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org