[
https://issues.apache.org/jira/browse/HDFS-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081657#comment-17081657
]
Xiaoqiao He commented on HDFS-15082:
------------------------------------
Thanks [~ayushtkn] for your comments. Yes, since we reused
DFS_NAMENODE_MAX_COMPONENT_LENGTH_KEY configuration key at Router side based on
v003, so it keeps this restriction when set configuration. IMO, we should add
description explicitly for DFS_NAMENODE_MAX_COMPONENT_LENGTH_KEY to end user
and suggest to set this configuration at Router side if NN side do that. What
do you think about or any other suggestions? Thanks.
> 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, HDFS-15082.002.patch,
> HDFS-15082.003.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
