cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Potekhin <>
Subject Re: Mass deletion -- slowing down
Date Mon, 14 Nov 2011 01:43:27 GMT

it won't work in my application, as I need a few indexes on attributes
of the job. In addition, a large portion of queries is based on key-value
lookup, and that key is the unique job ID. I really can't have data packed
in one row per day.


On 11/13/2011 8:34 PM, Brandon Williams wrote:
> On Sun, Nov 13, 2011 at 7:25 PM, Maxim Potekhin<>  wrote:
>> Each row represents a computational task (a job) executed on the grid or in
>> the cloud. It naturally has a timestamp as one of its attributes,
>> representing the time of the last update. This timestamp
>> is used to group the data into "buckets" each representing one day in the
>> system's activity.
>> I create the "DATE" attribute and add it to each row, e.g. it's a column
>> {'DATE','20111113'}.
> Hmm, so why is pushing this into the row key and then deleting the
> entire row not acceptable? (this is what the link I gave would
> prescribe)  In other words, you bucket at the row level, instead of
> relying on a column attribute that needs an index.
> -Brandon

View raw message