[
https://issues.apache.org/jira/browse/HDFS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627802#comment-13627802
]
Daryn Sharp commented on HDFS-4434:
-----------------------------------
bq. Related work for another Jira - .reserved should not be allowed anywhere.
Out of curiosity, what is the reasoning behind the need for the restriction?
I'm generally not a fan of adding restrictions on path names. If the NN used
URIs, then using something like inode://NNN/path would be cleaner and avoid
restrictions anywhere.
bq. We may want to allow chrooted file systems (note viewfs already has an
internal client side fs to support chrooted fs).
I'm not sure this is a good idea. It may allow the client to break out of the
chroot.
bq. [Re: referencing inodes in symlink target] I propose that you disallow
"/.reserved" in the target.
Completely agree.
For the sake of discussion, I'm actually starting to get a bit squeamish of
this change. By implementing this feature via special paths, I worry that user
code will begin to directly use these paths instead of only allowing the client
to use the feature. I seems that a simpler implementation would be for leases
to map the open paths to their inode id and use that mapping to resolve paths.
> Provide a mapping from INodeId to INode
> ---------------------------------------
>
> Key: HDFS-4434
> URL: https://issues.apache.org/jira/browse/HDFS-4434
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Brandon Li
> Assignee: Suresh Srinivas
> Attachments: HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch
>
>
> This JIRA is to provide a way to access the INode via its id. The proposed
> solution is to have an in-memory mapping from INodeId to INode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
