hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5847) Consolidate INodeReference into a separate section
Date Thu, 13 Feb 2014 00:01:23 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jing Zhao updated HDFS-5847:
----------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I've committed this.

> Consolidate INodeReference into a separate section
> --------------------------------------------------
>
>                 Key: HDFS-5847
>                 URL: https://issues.apache.org/jira/browse/HDFS-5847
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0
>            Reporter: Haohui Mai
>            Assignee: Jing Zhao
>             Fix For: 3.0.0
>
>         Attachments: HDFS-5847.000.patch, HDFS-5847.001.patch, HDFS-5847.002.patch
>
>
> Currently each INodeDirectorySection.Entry contains variable numbers of INodeReference
entries. The INodeReference entries are inlined, therefore it is difficult to quickly navigate
through a INodeDirectorySection.Entry. Skipping through a INodeDirectorySection.Entry without
parsing is essential to parse these entries in parallel.
> This jira proposes to consolidate INodeReferences into a section and give each of them
an ID. The INodeDirectorySection.Entry can store the list of the IDs as a repeated field.
That way we can leverage the existing code in protobuf to quickly skip through a INodeDirectorySection.Entry.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message