On Wed, May 29, 2013 at 9:33 AM, Hiller, Dean wrote:
> 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.
Compaction can only really efficiently multi-thread
Wednesday, May 29, 2013 10:01 AM
>To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
>mailto:user@cassandra.apache.org>>
>Subject: Re: Is there anyone who implemented time range partitions with
>column families?
>
>Thank you very much for the fast answer
Hello Cem,
You can get a similar effect by specifying a TTL value for data you save to
a table. If the data becomes older than the TTL value then it will
automatically be deleted by C*
Thanks
Jabbar Azam
On 29 May 2013 17:01, cem wrote:
> Thank you very much for the fast answer.
>
> Does pl
@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
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 Cassand
Thank you very much for the fast answer.
Does playORM use different column families for each partition in Cassandra?
Cem
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
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 o
Hi All,
I used time range partitions 5 years ago with MySQL to clean up data much
faster.
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 i
