You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ayush Saxena (Jira)" <ji...@apache.org> on 2019/12/29 07:20:00 UTC

[jira] [Commented] (HDFS-15082) RBF: Check each component length of destination path when add/update mount entry

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

Ayush Saxena commented on HDFS-15082:
-------------------------------------

is it similar to HDFS-13576?
Regarding the patch :
* Are we having a separate configuration at the Router to specify the path length independent of the namespace?
If so, I don't think it makes sense.
* The default should be 0, to disable this by default to ensure compatibility?
* What is the use case for having this, or say advantage of having this?

> RBF: Check each component length of destination path when add/update mount entry
> --------------------------------------------------------------------------------
>
>                 Key: HDFS-15082
>                 URL: https://issues.apache.org/jira/browse/HDFS-15082
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: rbf
>            Reporter: Xiaoqiao He
>            Assignee: Xiaoqiao He
>            Priority: Major
>         Attachments: HDFS-15082.001.patch
>
>
> When add/update mount entry, each component length of destination path could exceed filesystem path component length limit, reference to `dfs.namenode.fs-limits.max-component-length` of NameNode. So we should check each component length of destination path when add/update mount entry at Router side.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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