w which ones to delete or modify. Does one always
> need a separate column family to handle updating/deletion for time series, or
> is usually handled by setting TTL for data outside the archival period, or
> does time series modelling usually not involve any manipulation of past
> recor
t;
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Data Modelling Suggestions
I was tryin
> I was trying to find hector examples where we search for second column in a
> composite column, but I couldn't find any good one. Im not sure if its
> possible.…if you have any do have any example please share.
It's not. When slicing columns you can only return one contiguous range.
> Anyway
I think you need another CF as index.
user_itemid -> timestamped column_name
Otherwise you can't guess what's the timestamp to use in the column name.
Anyway I would prefer storing the item-ids as column names in the main
column family and having a second CF for the order-by-date query only with
Hi,
Need some help on a data modelling question. We're using Hector & Datastax
Enterprise 2.1.
I want to associate a list of items for a user. It should be sorted on the time
added. And items can be updated (quantity of the item can be changed), and
items can be deleted.
I can model it like t
