maybe not all nosql applications fit cassandra.

the whole core logic of how cassandra is eventually consistent is because of the per column timestamps... if they are a pain for you consider storing eg as a small number of fat columns rather than many skinny ones... either that or look at a different database for your use case. ;-)

- Stephen

---
Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen

On 3 Sep 2011 16:01, "Kevin Burton" <burton@spinn3r.com> wrote: