Caleb Rackliffe created CASSANDRA-17318:
-------------------------------------------
Summary: Runtime-configurable YAML option to prohibit USE
statements
Key: CASSANDRA-17318
URL: https://issues.apache.org/jira/browse/CASSANDRA-17318
Project: Cassandra
Issue Type: Improvement
Reporter: Caleb Rackliffe
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.)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
