To: "user@cassandra.apache.org"
Subject: Re: Cassandra Data Model with Narrow partition
Hi Chandra,
Narrow partition is probably your best choice, but you need to bucket data
somehow, otherwise your partitions will soon become unmanageable and you'll
have problems reading them, bo
agree with Carlos, you should bucket your key, for example, into (pk, day,
hour). Otherwise your partition is going to be large enough to cause
problems.
On Fri, Oct 30, 2015 at 8:04 AM, Carlos Alonso wrote:
> Hi Chandra,
>
> Narrow partition is probably your best choice, but you need to bucket
Hi Chandra,
Narrow partition is probably your best choice, but you need to bucket data
somehow, otherwise your partitions will soon become unmanageable and you'll
have problems reading them, both because the partitions will become very
big and also because of the tombstones that your expired recor
Hi,
Could you please suggest if Narrow partition is a good choice for the below
use case.
1) Write heavy event log table with 50m inserts per day with a peak load
of 20K transaction per sec. There aren't any updates/deletes to records
inserted. Records are inserted with a TTL of 60 days
