Hi Alain,
Thank you for your response.
In my case, counter is the main table, having almost 40% of all data.
Thank you for the recommendation about testing on one node.
2018-01-18 13:02 GMT+02:00 Alain RODRIGUEZ :
> Hello,
>
> I believe there is not a really specifically good strategy for counte
Hello,
I believe there is not a really specifically good strategy for counters.
Often counter tables size is relatively low (compared to events / raw
data). So depending on the workload you might want to pick one or the
other. Given the high number of reads the table will have to face (during
read
Hello!
I am using Cassandra 3.10.
I have a counter table, with the following schema and RF=1
CREATE TABLE edges (
src_id text,
src_type text,
source text
weight counter,
PRIMARY KEY ((src_id, src_type), source)
);
SELECT vs UPDATE requests ratio for this table is 0.1
READ vs W
