Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=subject
	:references:from:content-type:in-reply-to:message-id:date:to
	:content-transfer-encoding:mime-version; q=dns; s=
	thelastpickle.com; b=Kmaa1jd4pZmPgPPmwoB3uuPIypDKZfegY4G+nnPuuXX
	HWvZXo+gQ9EmZYpMHzcbhUIsm+mGYgPIzK3PR4YFoy1Gam8l81INbAaG/KN7H5e1
	B6wj3CPLG+hxQCacPO8irlzdDHh722XxaPI4RYkOdGrXO4I/RoL0MqOnzo/KGZT0
	=
Subject: Re: What would be a good strategy for Storing the large text contents
 like blog posts in Cassandra.
References: <AANLkTinYKrb_jPHkj_b6sWA0H-98h-eJeSY-6K8KFu1V@mail.gmail.com>
From: Aaron Morton <aaron@thelastpickle.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <AANLkTinYKrb_jPHkj_b6sWA0H-98h-eJeSY-6K8KFu1V@mail.gmail.com>
Message-Id: <FCB36084-B15C-4498-8194-E2F34D8BE5E0@thelastpickle.com>
Date: Mon, 7 Mar 2011 12:40:12 +1300
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPad Mail 8C148)

Sounds reasonable, one CF for the blog post one CF for the comments. You cou=
ld also use a single CF if you will often read the blog and the comments at t=
he same time. The best design is the one that suits how your app works, try o=
ne and be prepared to change.

Note that counters are only in the 0.8 trunk and are still under development=
, they are not going to be released for a couple of months.

Your per column data size is nothing to be concerned abut.

Hope that helps.
Aaron=20

On 7/03/2011, at 6:35 AM, Aditya Narayan <adynnn@gmail.com> wrote:

> What would be a good strategy to store large text content/(blog posts
> of around 1500-3000 characters)  in cassandra? I need to store these
> blog posts along with their metadata like bloggerId, blogTags. I am
> looking forward to store this data in a single row giving each
> attribute a single column. So one blog per row. Is using a single
> column for a large blog post like this a good strategy?
>=20
> 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 Protocol buffers) and
> stored in a single column,
> For storing the no. of likes of each comment itself,  I am planning to
> keep a counter_column, in the same row, for each comment that will
> hold an no. specifiying no. of 'likes' of that comment.
>=20
> Any suggestions on the above design highly appreciated.. Thanks.