[CASSANDRA-17318] Runtime-configurable YAML option to prohibit USE statements

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1-alpha1, 4.1
• Component/s: CQL/Syntax
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/28eea6e8cd4055c8d21f872c72f8bd14fd2467ba

Test and Documentation Plan

• new cassandra.yaml option w/ inline documentation
• new metrics around USE statement usage
• new CQLTester tests to verify enable/disable

• Assignee: Caleb Rackliffe
• Reporter: Caleb Rackliffe

Authors

Caleb Rackliffe

Reviewers

David Capwell

• Created: 27/Jan/22 23:49
• Updated: 27/May/22 19:25
• Resolved: 04/Feb/22 20:26

Description

The ambiguity around prepared statements without fully qualified table names has led to a number of sub-optimal outcomes for our users. With CASSANDRA-15252 and CASSANDRA-17248 resolved, there aren't any lingering known issues, but operators may still want to cordon USE statements off completely. This is especially important if we plan to deprecate and remove USE at some point in the future.

A couple details...

1.) The new option will be opt-in.
2.) It will be possible to change at runtime.
3.) There will be a new metric for USE that tells us whether it's been used at all. (This should make it easier to disable USE for an existing cluster where we don't know a-priori that it isn't in play.)