Thanks Tyler!
On Thu, Feb 3, 2011 at 12:06 PM, Tyler Hobbs wrote:
> On Wed, Feb 2, 2011 at 3:27 PM, Aditya Narayan wrote:
>>
>> Can I have some more feedback about my schema perhaps somewhat more
>> criticisive/harsh ?
>
> It sounds reasonable to me.
>
> Since you're writing/reading all of the
On Wed, Feb 2, 2011 at 3:27 PM, Aditya Narayan wrote:
> Can I have some more feedback about my schema perhaps somewhat more
> criticisive/harsh ?
>
It sounds reasonable to me.
Since you're writing/reading all of the subcolumns at the same time, I would
opt for a standard column with the tags se
Can I have some more feedback about my schema perhaps somewhat more
criticisive/harsh ?
Thanks again,
Aditya Narayan
On Wed, Feb 2, 2011 at 10:27 PM, Aditya Narayan wrote:
> @Bill
> Thank you BIll!
>
> @Cassandra users
> Can others also leave their suggestions and comments about my schema, plea
@Bill
Thank you BIll!
@Cassandra users
Can others also leave their suggestions and comments about my schema, please.
Also my question about whether to use a superColumn or alternatively,
just store the data (that would otherwise be stored in subcolumns) as
serialized into a single column in standa
I did not understand before... sorry.
Again, depending upon how many reminders you have for a single user, this could
be a long/wide row. Again, it really comes down to how many reminders are we
talking about and how often will they be read/written. While a single row can
contain millions (may
You got me wrong perhaps..
I am already splitting the row on per user basis ofcourse, otherwise
the schema wont make sense for my usage. The row contains only
*reminders of a single user* sorted in chronological order. The
reminder Id are stored as supercolumn name and subcolumn contain tags
for t
Any time I see/hear "a single row containing all ..." I get nervous. That single
row is going to reside on a single node. That is potentially a lot of load
(don't know the system) for that single node. Why wouldn't you split it by at
least user? If it won't be a lot of load, then why are you usi
I think you got it exactly what I wanted to convey except for few
things I want to clarify:
I was thinking of a single row containing all reminders (& not split
by day). History of the reminders need to be maintained for some time.
After certain time (say 3 or 6 months) they may be deleted by ttl
To reiterate, so I know we're both on the same page, your schema would be
something like this:
- A column family (as you describe) to store the details of a reminder. One
reminder per row. The row key would be a TimeUUID.
- A super column family to store the reminders for each user, for each
Actually, I am trying to use Cassandra to display to users on my
applicaiton, the list of all Reminders set by themselves for
themselves, on the application.
I need to store rows containing the timeline of daily Reminders put by
the users, for themselves, on application. The reminders need to be
p
10 matches
Mail list logo
