[ https://issues.apache.org/jira/browse/HDFS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626123#comment-13626123 ]
Sanjay Radia commented on HDFS-4434: ------------------------------------ bq. What happens if I start probing inode numbers? Can I find every path in the namespace, possibly ... Daryn, since the normal permission check is run on the full path, the resolution will fail at the same place it would have failed otherwise. That is, if you don't have "x-perm" on a dir /secretDir/ then the resolution will fail exactly at "/secretDir" and the exception will not give you any an additional info *as long as the exception does not returns the full path* (e.g. "/secretDir/a/b/c" ). > 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