You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Aravindan Vijayan (Jira)" <ji...@apache.org> on 2020/07/16 21:06:00 UTC
[jira] [Resolved] (HDDS-3924) Move away from proto serialization
for RocksDB keys in Ozone
[ https://issues.apache.org/jira/browse/HDDS-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aravindan Vijayan resolved HDDS-3924.
-------------------------------------
Resolution: Fixed
> Move away from proto serialization for RocksDB keys in Ozone
> ------------------------------------------------------------
>
> Key: HDDS-3924
> URL: https://issues.apache.org/jira/browse/HDDS-3924
> Project: Hadoop Distributed Data Store
> Issue Type: Task
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Blocker
>
> Currently there are a few places where we rely on protobuf serialization to convert the key type to byte array for a RocksDB column family 'key'. However, from the proto [documentation|https://developers.google.com/protocol-buffers/docs/encoding#implications] it looks like the serialization of proto is unreliable (especially across versions). If the byte[] got from proto serialization changes, this will be a problem since old keys will be unreadable.
> Thanks to [~arp] who helped unearth this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org