ultiple participants.
> >
> > ·Support full synch or delta synch based on number of
> > messages/history.
> >
> >
> >
> > I guess this makes the data model span across many CFs ?
> >
> >
> >
> >
> >
> >
e participants.
>
> ·Support full synch or delta synch based on number of
messages/history.
>
>
>
> I guess this makes the data model span across many CFs ?
>
>
>
>
>
>
>
>
>
> From: aaron morton [mailto:aa...@thelastpickle.c
*Support full synch or delta synch based on number of messages/history.
I guess this makes the data model span across many CFs ?
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: 06 February 2013 22:20
To: user@cassandra.apache.org
Subject: Re: DataModel Question
2) Dynami
ent: 06 February 2013 00:50
> To: user@cassandra.apache.org
> Subject: Re: DataModel Question
>
> Hi!
> I have couple of questions regarding your model:
>
> 1. What Cassandra version are you using? I am still working with 1.0 and
> this seems to make sense, but 1.2 gives you
1) Version is 1.2
2) DynamicComposites : I read somewhere that they are not recommended ?
3) Good point. I need to think about that one.
From: Tamar Fraenkel [mailto:ta...@tok-media.com]
Sent: 06 February 2013 00:50
To: user@cassandra.apache.org
Subject: Re: DataModel Question
Hi!
I have couple of questions regarding your model:
1. What Cassandra version are you using? I am still working with 1.0 and
this seems to make sense, but 1.2 gives you much more power I think.
2. Maybe I don't understand your model, but I think you need
DynamicComposite columns, as user column
Avoid super columns. If you need Sorted, wide rows then go for Composite
columns.
-Vivek
On Wed, Feb 6, 2013 at 7:09 AM, Kanwar Sangha wrote:
> Hi – We are designing a Cassandra based storage for the following use
> cases-
>
> ** **
>
> **·**Store SMS messages
>
> **·*
: user@cassandra.apache.org
Subject: DataModel Question
Hi - We are designing a Cassandra based storage for the following use cases-
* Store SMS messages
* Store MMS messages
* Store Chat history
What would be the ideal was to design the data model for this kind of
Hi - We are designing a Cassandra based storage for the following use cases-
*Store SMS messages
*Store MMS messages
*Store Chat history
What would be the ideal was to design the data model for this kind of
application ? I am thinking on these lines ..
Row-Key : Com
