one pro and one con.
>
> Is there any experience out there about such data modeling (option_a vs
> option_b) from the batch_mutate perspective ?
> Thanks.
>
> Dominique
>
>
>
> De : aaron morton [mailto:aa...@thelastpickle.com]
> Envoyé : mardi 9 avril
que
De : aaron morton [mailto:aa...@thelastpickle.com]
Envoyé : mardi 9 avril 2013 10:12
À : user@cassandra.apache.org
Objet : Re: data modeling from batch_mutate point of view
So, one alternative design for indexing CF could be:
rowkey = folder_id
colname = (indexed value, timestamp, file_i
> So, one alternative design for indexing CF could be:
> rowkey = folder_id
> colname = (indexed value, timestamp, file_id)
> colvalue = ""
>
If you always search in a folder what about
rowkey =
colname =
(That's closer to secondary indexes in cassandra with the addition of the
folder_id)
>
Hi,
I have a use case that sounds like storing data associated with files. So, I
store them with the CF:
rowkey = (folder_id, file_id)
colname = property name (about the file corresponding to file_id)
colvalue = property value
And I have CF for "manual" indexing:
rowkey = (folder_id, indexed val
