Using supercolumns to contain versions is reasonable, as long as the
number of versions is not too large.
On Sat, Feb 5, 2011 at 4:38 PM, Victor Kabdebon
wrote:
> Hello Raj,
>
> No it actually doesn't make sense from the point of view of Cassandra;
> OrderingPartioner preserves the order of the k
Hello Raj,
No it actually doesn't make sense from the point of view of Cassandra;
OrderingPartioner preserves the order of the *keys*. The Ordering will be
done according to the *supercolumn name*. In that case you can set the
ordering with compare_super_with (sorry I don't remember exactly the ne
Hi all -
We're new to Cassandra and have read plenty on the data model, but we wanted
to poll for thoughts on how to best handle this structure.
We have simple objects that have and ID and we want to maintain a history of
all the revisions.
e.g.
MyObject:
ID (long)
name
other fields
