[
https://issues.apache.org/jira/browse/HDFS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485837#comment-13485837
]
Jing Zhao commented on HDFS-4124:
---------------------------------
We may want to include a number indicating the actual number of elements in
INodesInPath. Currently in every place that calls getExistingPathINodes, the
capacity of INodesInPath's INode array is always <= the size of components,
thus to implement INodesInPath without the number seems fine. (However, based
on the logic in getExistingPathINodes, the capacity of INodesInPath is allowed
to be larger than the size of components. Thus I guess we may add this number
later or in the snapshot branch first.)
> Refactor INodeDirectory#getExistingPathINodes() to enable returning more than
> INode array
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-4124
> URL: https://issues.apache.org/jira/browse/HDFS-4124
> Project: Hadoop HDFS
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Priority: Minor
> Attachments: HDFS-INodeDirecotry.trunk.001.patch,
> HDFS-INodeDirecotry.trunk.002.patch
>
>
> Currently INodeDirectory#getExistingPathINodes() uses an INode array to
> return the INodes resolved from the given path. For snapshot we need the
> function to be able to return more information when resolving a path for a
> snapshot file/dir.
--
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
