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 rajkumar.w93@gmail.com
 designates 209.85.214.44 as permitted sender)
MIME-Version: 1.0
Sender: rajkumar.w93@gmail.com
In-Reply-To: 
 <CAP=kKf86et4pPtURPk66TvmOST4s3EqB1iovE4UCSx_FJb4s8Q@mail.gmail.com>
References: 
 <CANGD+ioHEskxEC0WiUb1OXatBJGvn0kLWktKusZ1ysSwi0P_kQ@mail.gmail.com>
	<1729105504170368002@unknownmsgid>
	<CANGD+io+VGNwi=0fUBG2y1pb+-+uozhTE7CN9VMh6Tkf7+jVcA@mail.gmail.com>
	<CAP=kKf86et4pPtURPk66TvmOST4s3EqB1iovE4UCSx_FJb4s8Q@mail.gmail.com>
Date: Wed, 16 Nov 2011 10:56:00 +0530
Message-ID: 
 <CANGD+iqLH7_nh9LSn=ueb8-3YnHwFPGrxSqVZyfw3SMvOp=dZA@mail.gmail.com>
Subject: Re: Seeking advice on Schema and Caching
From: Aditya Narayan <adynnn@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=000e0cdfcbc6dbc17d04b1d356d2

--000e0cdfcbc6dbc17d04b1d356d2
Content-Type: text/plain; charset=ISO-8859-1

Got the first option that you suggested.

However, In the second one, are you suggested to use, for e.g, key='Marcos'
& store cols, for all users of that name, containing userId inside that
row. That way it would have to read multiple rows while user is doing a
single search.

On Wed, Nov 16, 2011 at 10:47 AM, samal <samalgorai@gmail.com> wrote:

>
>  > I need to add 'search users' functionality to my application. (The
>>> trigger for fetching searched items(like google instant search) is made
>>> when 3 letters have been typed in).
>>> >
>>> > For this, I make a CF with String type keys. Each such key is made of
>>> first 3 letters of a user's name.
>>> >
>>> > Thus all names starting with 'Mar-' are stored in single row (with
>>> key="Mar").
>>> > The column names are framed as remaining letters of the names. Thus, a
>>> name 'Marcos' will be stored within rowkey "Mar" & col name "cos". The id
>>> will be stored as column value. Since there could be many users with same
>>> name. Thus I would have multple userIds(of users named "Marcos") to be
>>> stored inside columnname "cos" under key "Mar". Thus,
>>> >
>>> > 1. Supercolumn seems to be a better fit for my use case(so that ids of
>>> users with same name may fit as sub-columns inside a super-column) but
>>> since supercolumns are not encouraged thus I want to use an alternative
>>> schema for this usecase if possible. Could you suggest some ideas on this ?
>>> >
>>>
>>
> Aditya,
>
> Have you any given thought on Composite columns [1]. I think it can help
> you solve your problem of multiple user with same name.
>
> mar:{
>   {cos,unique_user_id}:unique_user_id,
>   {cos,1}:1,
>   {cos,2}:2,
>   {cos,3}:3,
>
> //  {utf8,timeUUID}:timeUUID,
> }
> OR
> you can try wide rows indexing user name to ID's
>
> marcos{
>    user1:' ',
>    user2:' ',
>    user3:' '
> }
>
> [1]http://www.slideshare.net/edanuff/indexing-in-cassandra
>
>

--000e0cdfcbc6dbc17d04b1d356d2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Got the first option that you suggested.<div><br></div><div>However, In the=
 second one, are you suggested to use, for e.g, key=3D&#39;Marcos&#39; &amp=
; store cols, for all users of that name, containing userId inside that row=
. That way it would have to read multiple rows while user is doing a single=
 search.<br>
<br><div class=3D"gmail_quote">On Wed, Nov 16, 2011 at 10:47 AM, samal <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:samalgorai@gmail.com">samalgorai@gmail.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div class=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div><div><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">


<div><div>
&gt; I need to add &#39;search users&#39; functionality to my application. =
(The trigger for fetching searched items(like google instant search) is mad=
e when 3 letters have been typed in).<br>
&gt;<br>
&gt; For this, I make a CF with String type keys. Each such key is made of =
first 3 letters of a user&#39;s name.<br>
&gt;<br>
&gt; Thus all names starting with &#39;Mar-&#39; are stored in single row (=
with key=3D&quot;Mar&quot;).<br>
&gt; The column names are framed as remaining letters of the names. Thus, a=
 name &#39;Marcos&#39; will be stored within rowkey &quot;Mar&quot; &amp; c=
ol name &quot;cos&quot;. The id will be stored as column value. Since there=
 could be many users with same name. Thus I would have multple userIds(of u=
sers named &quot;Marcos&quot;) to be stored inside columnname &quot;cos&quo=
t; under key &quot;Mar&quot;. Thus,<br>


&gt;<br>
&gt; 1. Supercolumn seems to be a better fit for my use case(so that ids of=
 users with same name may fit as sub-columns inside a super-column) but sin=
ce supercolumns are not encouraged thus I want to use an alternative schema=
 for this usecase if possible. Could you suggest some ideas on this ?<br>


&gt;<br></div></div></blockquote></div></div></div></div></blockquote></div=
><div><br>Aditya,<br><br>Have you any given thought on Composite columns [1=
]. I think it can help you solve your problem of multiple user with same na=
me. <br>


<br>mar:{<br>=A0 {cos,unique_user_id}:unique_user_id,<br>=A0 {cos,1}:1,<br>=
=A0  {cos,2}:2,<br>=A0 {cos,3}:3,<br><br>//=A0 {utf8,timeUUID}:timeUUID,<br=
>}<br>OR<br>you can try wide rows indexing user name to ID&#39;s<br><br>mar=
cos{<br>


=A0=A0 user1:&#39; &#39;,<br>=A0=A0 user2:&#39; &#39;,<br>=A0=A0 user3:&#39=
; &#39;<br>}<br><br>[1]<a href=3D"http://www.slideshare.net/edanuff/indexin=
g-in-cassandra" target=3D"_blank">http://www.slideshare.net/edanuff/indexin=
g-in-cassandra</a><br>

<br></div>
</div>
</blockquote></div><br></div>

--000e0cdfcbc6dbc17d04b1d356d2--