That scenario can result in slower reads than narrow rows that are updated less frequently.
Like most things it depends. Do you have a feel for how wide and what the update pattern is like ? Things like levelled compaction (http://www.datastax.com/dev/blog/leveled-compaction-in-apache-cassandra) can help. It's also pretty easy to run up a proof of concept to see what the read performance is like. Hope that helps. ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 15/05/2012, at 9:32 PM, Praveen Baratam wrote: > Hello Everybody, > > In my use case we use Wide Rows whose columns are frequently updated, deleted > and created. > > I was wondering if this case fits the Cassandra pattern and if there are any > precautions to be taken. > > Kindly advice! > > Praveen
