Thanks Aaron & Chris, I appreciate your help. With dedicated CF for counters, in addition to the issue pointed by Chris, the major drawback I see is that I cant read *in a single query* the counters with the regular columns row which is widely required by my application. My use case is like storing & reading the 'views count' of a post along with other post details(like post content,postedBy etc) in my application. I wanted to store the views count(*counter column*) along with the details of the post.
On Thu, Jul 14, 2011 at 10:20 PM, Chris Burroughs <chris.burrou...@gmail.com > wrote: > On 07/13/2011 03:57 PM, Aaron Morton wrote: > > You can always use a dedicated CF for the counters, and use the same row > key. > > Of course one could do this. The problem is you are now spending ~2x > disk space on row keys, and app specific client code just became more > complicated. >
