I suggest checking out Aaron Morton's post on the 3.0 storage engine.
https://thelastpickle.com/blog/2016/03/04/introductiont-to-the-apache-cassandra-3-storage-engine.html
On Tue, Dec 31, 2019 at 11:20 AM Subroto Barua
wrote:
> I have a table ---
>
> create Table mytable (
>
> Id text,
>
> cdat
I have a table ---
create Table mytable (
Id text,
cdate timestamp,
Tk text,
Primary key (id, cdate)
) with clustering order by (cdate desc);
One of the partition key has 2,099,414 rows; using the following formula:
row_size = sum_of_all_columns_ size_within_row + partition_key_size
row_size
Also, depends on type of var a and var b. If they are text, the byte size
will be different than an int, or watch out for counters, as that will mess
everything up.
On Tue, Dec 31, 2019 at 1:34 AM Dipan Shah wrote:
> Hello lampahome,
>
> Data will be compressed but you will also have to account
Hello lampahome,
Data will be compressed but you will also have to account for the replication
factor that you will be using.
Thanks,
Dipan Shah
From: lampahome
Sent: Tuesday, December 31, 2019 8:06 AM
To: user@cassandra.apache.org
Subject: How bottom of cas