Re: What would be a good strategy for Storing the large text contents like blog posts in Cassandra.

On 03/07/2011 10:08 PM, Aaron Morton wrote: You can fill your boots. So long as your boots have a capacity of 2 billion. Background ... http://wiki.apache.org/cassandra/LargeDataSetConsiderations http://wiki.apache.org/cassandra/CassandraLimitations

Re: What would be a good strategy for Storing the large text contents like blog posts in Cassandra.

Hello, On 03/06/2011 06:35 PM, Aditya Narayan wrote: Next, I also need to store the blogComments which I am planning to store all, in another single row. 1 comment per column. Thus the entire information about the a single comment like commentBody, commentor would be serialized(using google

Re: What would be a good strategy for Storing the large text contents like blog posts in Cassandra.

You can fill your boots. So long as your boots have a capacity of 2 billion. Background ... http://wiki.apache.org/cassandra/LargeDataSetConsiderations http://wiki.apache.org/cassandra/CassandraLimitations

Re: What would be a good strategy for Storing the large text contents like blog posts in Cassandra.

Sounds reasonable, one CF for the blog post one CF for the comments. You could also use a single CF if you will often read the blog and the comments at the same time. The best design is the one that suits how your app works, try one and be prepared to change. Note that counters are only in the

Re: What would be a good strategy for Storing the large text contents like blog posts in Cassandra.

Thanks Aaron!! I didnt knew about the upcoming facility for inbuilt counters. This sounds really great for my use-case!! Could you let me know where can I read more about this, if this had been blogged about, somewhere ? I'll go forward with the one (entire)blog per column design. Thanks On