cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean" <>
Subject Re: Is there anyone who implemented time range partitions with column families?
Date Wed, 29 May 2013 16:33:20 GMT
Something we just ran into with compaction and timeseries data.  We have
60,000 virtual tables(playorm virtual tables) inside ONE CF.  This
unfortunately hurt our compaction with LCS since it can't be parallized
for a single tier.  We should have had 10 CF's called data0, data1, data2
Š.data9 such that we could be running 10 compactions in parallel.

QUESTION: I am assuming 10 compactions should be enough to put enough load
on the disk/cpu/ram etc. etc. or do you think I should go with 100CF's.
98% of our data is all in this one CF.


On 5/29/13 10:06 AM, "Hiller, Dean" <> wrote:

>Nope, partitioning is done per CF in PlayOrm.
>From: cem <<>>
>Reply-To: "<>"
>Date: Wednesday, May 29, 2013 10:01 AM
>To: "<>"
>Subject: Re: Is there anyone who implemented time range partitions with
>column families?
>Thank you very much for the fast answer.
>Does playORM use different column families for each partition in
>On Wed, May 29, 2013 at 5:30 PM, Jeremy Powell
><<>> wrote:
>Cem, yes, you can do this with C*, though you have to handle the logic
>yourself (other libraries might do this for you, seen the dev of playORM
>discuss some things which might be similar).  We use Astyanax and
>programmatically create CFs based on a time period of our choosing that
>makes sense for our system, programmatically drop CFs if/when they are
>outside a certain time period (rather than using C*'s TTL), and write
>data to the different CFs as needed.
>On Wed, May 29, 2013 at 8:36 AM, cem
><<>> wrote:
>Hi All,
>I used time range partitions 5 years ago with MySQL to clean up data much
>I had a big FACT table with time range partitions and it was very is to
>drop old partitions (with archiving) and do some saving on disk.
>Has anyone implemented such a thing in Cassandra? It would be great if we
>have that in Cassandra.
>Best Regards,

View raw message