[
https://issues.apache.org/jira/browse/HDFS-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498654#comment-17498654
]
Íñigo Goiri commented on HDFS-16487:
------------------------------------
[~fengnanli] if I understand your setup, something like HDFS-13506 would fix
the issue as the folder would be created when creating the mount point, right?
If that's the case, we should go down that path.
Then, the question is the permissions for the folder created.
We can either provided in the command line when creating or have a default
value that can be specified in the rbf config file.
> 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: Aihua Xu
> 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: [email protected]
For additional commands, e-mail: [email protected]
