Hello Bowen, Arvydas,
Thanks for your answers.
May I clarify things about compaction. If I have a table with LCS with
160MB of sstable size target, if a partition has many rows so that the
total size of the partition is greater than 160MB, then there will
eventually be an sstable greater than
Sebastien,
Another thing to keep in mind when writing/updating a map column is that it
is internally (in the memtable) backed by a synchronized data structure -
if the rate of writes/updates is sufficiently high, the resulting CPU load
will cripple the nodes (see CASSANDRA-15464
Hi Sebastien,
It's a bit more complicated than that.
To begin with, the first-class citizen in Cassandra is partition, not
row. All map fields in the same row are in the same partition, and all
rows with the same partition key but different clustering keys are also
in the same partition.
Hello
If i have a colum of type Map, then with many insertions, the map grows,
but after compation, as the full map is 1 column of a table, will it be
contained fully in 1 SSTable?
I guess yes cause the map is contained in a single row. Am I right?
Versus if we use a clustering key + a standard