But in the case of simple column family I've the same problem when I update the score of 1 user then I need to remove his old score too. For example here the user uid5 was at 130 now he is at 140 because I add the random number cassandra will keep all the score evolution.
get Keyspace2.topScoreUser['top'] => (column=140-1, value=uid5, timestamp=1268841641979) => (column=130-2, value=uid5, timestamp=1268841614066) => (column=130-1, value=uid4, timestamp=1268841594786) => (column=130, value=uid4, timestamp=1268841517352) => (column=120, value=uid3, timestamp=1268841509536) => (column=110, value=uid2, timestamp=1268841501720) => (column=100, value=uid1, timestamp=1268841496069) Is it wrong ? On Wed, Mar 17, 2010 at 6:20 PM, Brandon Williams <dri...@gmail.com> wrote: > On Wed, Mar 17, 2010 at 11:13 AM, Toby DiPasquale <t...@cbcg.net> wrote: >> >> Couldn't you just use a supercolumn whose keys were the score and the >> subcolumns were username:true? Basically using the subcolumns as a >> list? >> > > Sure, but that complicates getting the top N scores. You'd have to use the > OrderedPartioner, so it's a bit less flexible. Also, any time a score > changed you'd have to find the old one and remove them. > > -Brandon >
