Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of sdolgy@gmail.com designates
 209.85.216.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=vpBmes6WKn9WjIhQMM6TIM9DnZN6Zh43c4n0RoHWlh0jfhTo+UvjtZg1OYpCAplfDp
         OW4ov3dTKDT9rj48D+caSn0l5WtZi7r5vl7ZLmTrv5j8Odzqv/LP3kB2pNzxD9cTBZSM
         0C9v39fx+SyTeSv9GsVuxQ7c9ZWTYduEAzrPc=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=PRNTRMR6pVOTZaChvc=u0sbSs=cdP0cgmTFzK@mail.gmail.com>
References: <AANLkTi=6bLtjCysSjCHTXbi9xxVJ=EQcCwWVt5WCXvB6@mail.gmail.com>
 <AANLkTi=cjq5vyyShrQnzYi0FY-7bJ-TXVEJhcr6ScU1Z@mail.gmail.com>
 <AANLkTi=PRNTRMR6pVOTZaChvc=u0sbSs=cdP0cgmTFzK@mail.gmail.com>
From: Sasha Dolgy <sdolgy@gmail.com>
Date: Tue, 15 Feb 2011 14:49:44 +0100
Message-ID: <AANLkTikA=ps9BL0--t02un66O1S9jMxH6h8ZUdnVrdbS@mail.gmail.com>
Subject: Re: online chat scenario
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0016e68b68b20d5735049c527124

--0016e68b68b20d5735049c527124
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

thanks for the response.  thinking about this, this would not allow for the
sorting of messages into a chronological order for end user display.  i had
thought about having each message as its own column against the room or the
user, but i have had some inconsistencies in retrieving the data.  sometime=
s
i get 3 columns, sometimes i get 50...( i think this is because of the
random partitioner)

i had thought about this structure:

[messages][nickname][message id =3D> message data]
[chatrooms][room_name][message id]

this way i can pull all messages a user ever posted, not specific to a
room.  what i haven't been able to do so far is print the timestamp on the
row or column.  does this have to be explicitly added somewhere or can it b=
e
returned as part of a 'get' request?

-sd


On Tue, Feb 15, 2011 at 2:12 PM, Michal August=FDn
<augustyn.michal@gmail.com>wrote:

> The schema design depends on chatrooms/users/messages numbers. I.e. you c=
an
> have one CF, where key is chatroom, column name is username, column value=
 is
> the message and message time is the same as column timestamp.
> You can add day-timestamp to the chatroom name to avoid large rows.
>
> Augi
>
> 2011/2/15 Andrey V. Panov <panov.andy@gmail.com>
>
> I never did it. But I suppose you can use "chatroom name" as key and stor=
e
>> messages & nicks as columns in JSON and timestamp as columnName.
>>
>
>


--=20
Sasha Dolgy
sasha.dolgy@gmail.com

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

<div>thanks for the response.=A0 thinking about this, this would not allow =
for the sorting of messages into a chronological order for end user display=
.=A0 i had thought about having each message as its own column against the =
room or the user, but i have had some inconsistencies in retrieving the dat=
a.=A0 sometimes i get 3 columns, sometimes i get 50...( i think this is bec=
ause of the random partitioner)</div>


<div>=A0</div>
<div>i had thought about this structure:</div>
<div>=A0</div>
<div>[messages][nickname][message id =3D&gt; message data]</div>
<div>[chatrooms][room_name][message id]</div>
<div>=A0</div>
<div>this way i can pull all messages a user ever posted, not specific to a=
 room.=A0 what i haven&#39;t been able to do so far is print the timestamp =
on the row or column.=A0 does this have to be explicitly added somewhere or=
 can it be returned as part of a &#39;get&#39; request?=A0 </div>


<div>=A0</div>
<div>-sd</div>
<div>=A0</div>
<div>=A0</div>
<div class=3D"gmail_quote">On Tue, Feb 15, 2011 at 2:12 PM, Michal August=
=FDn <span dir=3D"ltr">&lt;<a href=3D"mailto:augustyn.michal@gmail.com">aug=
ustyn.michal@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The schema design depends on cha=
trooms/users/messages numbers. I.e. you can have one CF, where key is chatr=
oom, column name is username, column value is the message and message time =
is the same as column timestamp.=20
<div>You can add day-timestamp to the chatroom name to avoid large rows.<br=
>
<div><br></div>
<div>Augi<br><br>
<div class=3D"gmail_quote">2011/2/15 Andrey V. Panov <span dir=3D"ltr">&lt;=
<a href=3D"mailto:panov.andy@gmail.com" target=3D"_blank">panov.andy@gmail.=
com</a>&gt;</span>=20
<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I never did it. But I suppose yo=
u can use &quot;chatroom name&quot; as key and store messages &amp; nicks a=
s columns in JSON and timestamp as columnName.<br>

</blockquote></div></div><br></div></div></blockquote></div><br><br clear=
=3D"all"><br>-- <br>Sasha Dolgy<br><a href=3D"mailto:sasha.dolgy@gmail.com"=
 target=3D"_blank">sasha.dolgy@gmail.com</a><br>

--0016e68b68b20d5735049c527124--