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: domain of bill.speirs@gmail.com
 designates 209.85.213.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=bMoHrIV1dFQ6AoC2U+4bmtJznjlDcyOQkbVEebCl5/Y/3adGPkSsRtCgJxxHwRd44j
         4SvLmjpTSyLOCN4mtBjFkVKLa5wh8v/bCr0FdtajRwxFFb+DX7O4XA6XzWVFApbHTfgH
         rtcSZoxezbQdc4OeMyvwU3R7W4ONjHZS2v3Gg=
MIME-Version: 1.0
In-Reply-To: <loom.20110211T102449-570@post.gmane.org>
References: <loom.20110211T102449-570@post.gmane.org>
Date: Fri, 11 Feb 2011 10:14:06 -0500
Message-ID: <AANLkTi=tVK2g0WHd5ggyfAdJsYOMV7Oj2WymQ2nVMjHY@mail.gmail.com>
Subject: Re: How to store news lists in optimal way?
From: Bill Speirs <bill.speirs@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I don't know enough about Lucene to comment, but option #2 seems like
a bad idea. You shouldn't grow your database by the number of Column
Families as there are bad implications to doing this. Option #1 or #3
seems plausible depending upon how much data you have.

Hope this helps...

Bill-

On Fri, Feb 11, 2011 at 4:26 AM, Nikolay Fominyh <nikolayfn@gmail.com> wrot=
e:
> Hello.
>
> We have a problem with finding way to store user news list.
> Our task - we have 2 group of filters:
> 1) News Types(photo, video, audio, etc... )
> 2) User Lists(user, friends, friends friends, etc..)
>
> Our solution ways:
> 1) Store matrix of filters for each user.
> UserNews:
> =A0 user_id1:
> =A0 =A0 =A0 =A0<list_type1>: (date, uuid)
> =A0 =A0 =A0 =A0<list_type1>_<news_type1>: list(date, news_uuid)
> =A0 =A0 =A0 =A0<list_type1>_<news_type2>: list(date, news_uuid)
> =A0 =A0 =A0 =A0....
> =A0 =A0 =A0 =A0<list_typeN>: (date, uuid)
> =A0 =A0 =A0 =A0<list_typeN>_<news_type1>: list(date, news_uuid)
> =A0 =A0 =A0 =A0<list_typeN>_<news_type2>: list(date, news_uuid)
> =A0 =A0 =A0 =A0...
> =A0 ...
> =A0 user_idN:
> =A0 =A0 =A0 =A0<list_type1>: (date, uuid)
> =A0 =A0 =A0 =A0<list_type1>_<news_type1>: list(date, news_uuid)
> =A0 =A0 =A0 =A0<list_type1>_<news_type2>: list(date, news_uuid)
> =A0 =A0 =A0 =A0....
> =A0 =A0 =A0 =A0<list_typeN>: (date, uuid)
> =A0 =A0 =A0 =A0<list_typeN>_<news_type1>: list(date, news_uuid)
> =A0 =A0 =A0 =A0<list_typeN>_<news_type2>: list(date, news_uuid)
> =A0 =A0 =A0 =A0...
>
> Numbers of filters in this way more than 100..
>
> 2) Store news lists for each user in personal column family.
> UserNews_<id>:
> =A0 =A0date_uuid:
> =A0 =A0 =A0 =A0<news_type> : indexed
> =A0 =A0 =A0 =A0<list_type> : indexed
> =A0 =A0 =A0 =A0<news_uuid>
>
> In this case we have huge number of column families.
>
> 3) Store news lists in SQL Database and News in Cassandra.
>
> 4) Use Apache Lucene for indexes on filters.
>
> Question: What of this ways is most optimal? Is there another ways of sol=
utuion?
>
>