cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Terje Marthinussen (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3024) sstable and message varint encoding
Date Tue, 13 Sep 2011 02:01:09 GMT


Terje Marthinussen commented on CASSANDRA-3024:

I have ported stuff related to handling this for columns/supercolumns (requires changes to
size calculations as well) including more dense timestamp handling.

I was looking quickly at the sstables as well as other places where we write short/ints/longs
and I started realizing that modifying all of this gets a bit of a work.

What about changing RandomAccessReader to something like (Descriptor desc,...) rather than
(File file, ....) and adding backwards compatibility there for fixed length/ variable length
readInt/Long there?

On the write side, modify SequentialWriter with overrides for variable length write methods.

Any objections against doing this at such a "low" level?

> sstable and message varint encoding
> -----------------------------------
>                 Key: CASSANDRA-3024
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.1
> 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:


View raw message