-Re: [VOTE] Merge HDFS-5698 Use protobuf to serialize / deserialize FSImage to trunk
Thank you, Haohui Mai and Jing Zhao. I'm definitely looking forward to
fewer metadata upgrades in the future. :-)
On Mon, Feb 3, 2014 at 10:49 PM, Akira AJISAKA
> +1 (non-binding).
> This feature is very good for the developers to reduce
> the tasks for supporting FSImage compatibility.
> (2014/01/31 7:37), Haohui Mai wrote:
>> Hello all,
>> I would like to call a vote to merge of the new protobuf-based FSImage
>> The changes introduce a protobuf-based FSImage format into HDFS. It
>> separates the responsibility of serializing and reconstructing the
>> namespace in the NameNode using Google's Protocol Buffers
>> (protobuf). The new FSImage delegates much parts of the serialization /
>> deserialization logics to the protobuf side. It is also designed to
>> improve the supports for compatibility and interoperability.
>> The development has been done in a separate branch:
>> The design document is available at:
>> The HDFS-5698 jira tracks the development of the feature.
>> The feature changes no public APIs. The existing tests include both
>> unit tests and end-to-end tests. They have already covered this
>> Once the feature is merged into trunk, we will continue to test and
>> fix any bugs that may be found on trunk.
>> The bulk of the design and implementation was done by Jing Zhao,
>> Suresh Srinivas and me. Thanks Kihwal Lee, Todd Lipcon, Colin
>> Patrick McCabe, Chris Nauroth, and Daryn Sharp for providing feedback on
>> the jiras and in discussions.
>> This vote runs for a week and closes on 2/6/2013 at 11:59 pm PT.
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.