Sure….. I'm willing to concede that Cassandra isn't for anyone but why make it worse than it has to be?
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. ;-)
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 screenOn 3 Sep 2011 16:01, "Kevin Burton" <email@example.com> wrote:
Location: San Francisco, CA
Skype-in: (415) 871-0687