As a general, rough guideline, I would suggest that a partition be kept
down to thousands or tens of thousands of rows, probably not more than 100K
rows per partition, and physical size kept to tens of thousands to hundreds
of thousands or maybe a few megabytes or ten megabytes maximum per
you might want to read here
http://wiki.apache.org/cassandra/CassandraLimitations
jason
On Fri, Feb 27, 2015 at 2:44 PM, wateray wate...@163.com wrote:
Hi all,
My team is using Cassandra as our database. We have one question as below.
As we know, the row with the some partition key will be
Also, note that repairs will be slower for larger rows and AFAIK also
require slightly more memory. Also, to avoid many tombstones it could be
worth to consider bucketing your partitions by time.
Cheers,
Jens
On Fri, Feb 27, 2015 at 7:44 AM, wateray wate...@163.com wrote:
Hi all,
My team is
application, IMHO.
-Marcelo
From: user@cassandra.apache.org
Subject: Re: how many rows can one partion key hold?
you might want to read here
http://wiki.apache.org/cassandra/CassandraLimitations
jason
On Fri, Feb 27, 2015 at 2:44 PM, wateray wate...@163.com wrote:
Hi all,
My team is using
Hi all,
My team is using Cassandra as our database. We have one question as below.
As we know, the row with the some partition key will be stored in the some node.
But how many rows can one partition key hold? What is it depend on? The node's
volume or partition data size or partition rows
