The same table name with two different CF IDs is not just "temporary
schema disagreements", it's much worse than that. This breaks the
eventual consistency guarantee, and leads to silent data corruption.
It's silently happening in the background, and you don't realise it
until you suddenly do,
The last time you mentioned this:
On Tue, Dec 5, 2023 at 11:57 AM Sébastien Rebecchi
wrote:
> Hi Bowen,
>
> Thanks for your answer.
>
> I was thinking of extreme use cases, but as far as I am concerned I can
> deal with creation and deletion of 2 tables every 6 hours for a keyspace.
> So it
Hi Bowen,
Thanks for your answer.
I was thinking of extreme use cases, but as far as I am concerned I can
deal with creation and deletion of 2 tables every 6 hours for a keyspace.
So it lets around 8 folders of deleted tables per day - sometimes more
cause I can see sometimes 2 folders created
I can't think of a reason to keep empty directories around, seems like a
reasonable change, but I don't think you're butting up against a thing that
most people would run into, as snapshots are enabled by default (auto_snapshot:
true) and almost nobody changes it.
The use case you described
The Cassandra team is pleased to announce the release of Apache Cassandra
version 5.0-beta1.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
Downloads of source and binary distributions are
Please rethink your use case. Create and delete tables concurrently
often lead to schema disagreement. Even doing so on a single node
sequentially will lead to a large number of tombstones in the system tables.
On 04/12/2023 19:55, Sébastien Rebecchi wrote:
Thank you Dipan.
Do you know if
