Thanks for the links. I wanted to avoid a major compaction somehow.

I see many JIRA issues on timestamps related to compaction/reads. So many
improvements have been proposed.

--
Ravi


On Thu, Oct 10, 2013 at 12:26 AM, Shahab Yunus <shahab.yu...@gmail.com>wrote:

> Ahh, yes, 'compaction'. I blanked out while mentioning repair and cleanup.
> That is in fact what needs to be done first and what I meant. Thanks
> Robert.
>
> Regards,
> Shahab
>
>
> On Wed, Oct 9, 2013 at 1:50 PM, Robert Coli <rc...@eventbrite.com> wrote:
>
>> On Wed, Oct 9, 2013 at 7:35 AM, Ravikumar Govindarajan <
>> ravikumar.govindara...@gmail.com> wrote:
>>
>>> What is the quick way to delete old-data and at the same time make sure
>>> read [doesn't] churn through all deleted columns?
>>>
>>
>> Use a database that isn't log structured?
>>
>> But seriously, in 2.0 there's this :
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-5514
>>
>> Which allows for timestamp hints at query time.
>>
>> And...
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-5228
>>
>> Which does compaction expiration of entire SSTables based on TTL.
>>
>> =Rob
>>
>>
>

Reply via email to