Re: Timeseries data

2013-03-31 Thread aaron morton
> I think if you use Level compaction, the number of sstables you will touch > will be less because sstables in each level is non overlapping except L0. You will want to do some testing because LCS uses extra IO to make those guarantees. You will also want to look at the SSTable size with LCS if

Re: Timeseries data

2013-03-28 Thread sankalp kohli
I think if you use Level compaction, the number of sstables you will touch will be less because sstables in each level is non overlapping except L0. On Wed, Mar 27, 2013 at 8:20 PM, aaron morton wrote: > sstablekey can help you find which sstables your keys are in. > > But yes, a slice call will

Re: Timeseries data

2013-03-27 Thread aaron morton
sstablekey can help you find which sstables your keys are in. But yes, a slice call will need to read from all sstables the row has a fragment in. This is one reason we normally suggest partitioning time series data by month or year or something sensible in your problem domain. You will proba

Re: Timeseries data

2013-03-27 Thread Bryan Talbot
In the worst case, that is possible, but compaction strategies try to minimize the number of SSTables that a row appears in so a row being in ALL SStables is not likely for most cases. -Bryan On Wed, Mar 27, 2013 at 12:17 PM, Kanwar Sangha wrote: > Hi – I have a query on Read with Cassandra.

Timeseries data

2013-03-27 Thread Kanwar Sangha
Hi - I have a query on Read with Cassandra. We are planning to have dynamic column family and each column would be on based a timeseries. Inserting data - key => ‘xxx′, {column_name => TimeUUID(now), :column_value => ‘value’ }, {column_name => TimeUUID(now), :column_value => ‘value’ },..