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 everyone,It was great seeing everyone who could attend the Cassandra
Summit last week. Thanks to everyone that helped make it successful.
Speakers. Attendees. Sponsors. You all had your role at bringing this back.
For those who couldn’t attend, every talk was recorded and is now up on the
LF
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
