Skip to content

Conversation

@bdeggleston
Copy link
Member

No description provided.

@maedhroz maedhroz changed the title C20926 mutation tracking config CASSANDRA-20926 mutation tracking config Dec 11, 2025
if (SchemaConstants.isSystemKeyspace(keyspaceName))
throw ire("Mutation tracking is not supported on system keyspaces");

if (!DatabaseDescriptor.getMutationTrackingEnabled())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need to move this, and probably some of the other pre-existing validation, out of apply and into validate.
DDL statements are encoded as entries in the metadata log and once committed must be able to be applied by all nodes, so divergent config across instances would create an issue here.
Also, log entries may be replayed after a bounce and changes to config could interfere with that & prevent the node from coming back up (c.f. CASSANDRA-20452)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@beobal Thanks for the note. I'm going to pick this up soon...

if (SchemaConstants.isSystemKeyspace(keyspaceName))
throw ire("Mutation tracking is not supported on system keyspaces");

if (!DatabaseDescriptor.getMutationTrackingEnabled())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same point as on AlterKeyspaceStatement applies here

@maedhroz
Copy link
Contributor

Closed in favor of #4559, but the open comments in this PR still need to be addressed...

@maedhroz maedhroz closed this Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants