If you're talking about logged batches, these absolutely have an impact on
performance of about 30%. The whole batch will succeed or fail as a unit,
but throughput will go down and load will go up. Keep in mind that logged
batches are atomic but are not isolated - i.e. it's totally possible to ge
""Get me the count of orders changed in a given sequence-id range"" --> Can
you give an example of SELECT statement for this query ?
Because given the table structure, you have to provide the shard-and-date
partition key and I don't see how you can know this value unless you create
as many SELECT
I currently have a keyspace with table definition that looks like this.
CREATE TABLE *orders*(
order-id long PRIMARY KEY,
order-blob text
);
This table will have a write load of ~40-100 tps and a read load of
~200-400 tps.
We are now considering adding another table definition which closely
