[
https://issues.apache.org/jira/browse/CASSANDRA-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086200#comment-13086200
]
Vladimir Loncar commented on CASSANDRA-3024:
--------------------------------------------
Implementing this requires changing (de)serialize methods to use VInt and
VLong. Now, while this works on new (empty) nodes, it of course breaks
deserialization of existing SSTables (and hence most tests right now fail).
What is the preferred approach to versioning serialization? I looked into
adding new version into Descriptor, but now I need to somehow pass that
information to serializers. I thought about adding descriptor parameter to
them, so that serializers know whether to use readInt(Long) or readVInt(VLong).
Also, should i only be worried about deserialization, or also serialization?
(If serialization always uses latest version, we shouldn't worry about it?).
> sstable and message varint encoding
> -----------------------------------
>
> Key: CASSANDRA-3024
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3024
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 1.0
>
>
> We could save some sstable space by encoding longs and ints as vlong and
> vint, respectively. (Probably most "short" lengths would be better as vint
> as well.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
