[
https://issues.apache.org/jira/browse/HDFS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628046#comment-13628046
]
Suresh Srinivas commented on HDFS-4434:
---------------------------------------
bq. 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.
Currently I plan to keep this as "private" and "unstable" feature and not make
it part of the public API. We plan to use this in NFS work, as a project
private feature.
bq. 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.
This is not just lease related. If you see the description in HDFS-4489, one of
the uses is to uniquely identify file for lease purposes. This has other uses
as well, as described in that jira.
bq. It's also something I'm planning to do in the next few months to reduce the
unnecessary work and garbage littering.
I do not think necessarily the existing code causes garbage littering. I have
been planning to move this to outside the lock for doing less holding the lock.
If you would like to do it, please go ahead. It will be a good change.
> 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
