Ok, thanks. I'm going with Option 1, and try to steer away from
SuperColumns. That also gives me the option to tweak the caches
depending on the use pattern (User CF will be accessed in a lot of
different ways, not just with relation to Objects).
/Janne
On Sep 14, 2010, at 23:46 , Aaron
I've been doing option 1 under 0.6. As usual in cassandra though a lot depends on how you access the data. - If you often want to get the user and all of the objects they have, use option 2. It's easier to have one read from one CF to answer your query. - If the user has potentially >10k objects go
Hi all!
I'm pondering between a couple of alternatives here: I've got two CFs, one
which contains Objects, and one which contains Users. Now, each Object has an
owner associated to it, so obviously I need some sort of an index to point from
Users to Objects. This would be of course the perfect
