You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/03/18 15:12:33 UTC

[jira] [Resolved] (CASSANDRA-3024) sstable and message varint encoding

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

Aleksey Yeschenko resolved CASSANDRA-3024.
------------------------------------------
       Resolution: Fixed
         Assignee:     (was: Vijay)
    Fix Version/s:     (was: 3.x)

With CASSANDRA-8099 and a bunch of follow-up tickets we now use varint encoding in most places where it makes sense.

> sstable and message varint encoding
> -----------------------------------
>
>                 Key: CASSANDRA-3024
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3024
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Priority: Minor
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)