If you go this route, be sure to take a look at the custom column comparator I wrote to make this sort of thing easier:
https://github.com/edanuff/CassandraCompositeType On Wed, Dec 1, 2010 at 4:56 AM, Daniel Lundin <d...@eintr.org> wrote: > You could also use a standard column family, composing the version > into the column name: > > foo => { bar:v1 => data, bar:v2 => data, bar:v3 => data } > > Here, there's a cost on retrieval of course, which may or may not work > depending on your access pattern. If you do large slices, it's > probably not an option. It could be feasible to write a custom > comparator sorting on some version component, to allow efficient > slicing of the "latest" versions. > >
