[
https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480207#comment-17480207
]
Benedict Elliott Smith commented on CASSANDRA-17188:
----------------------------------------------------
bq. I don't know if the idea here is reverting any new property since 4.0 and
block until we have that discussion
Have any new properties been created that relate to existing properties, and
have they done so in a manner that is inconsistent with existing or planned
near-term work? If so, yes they should be revisited.
I'm kind of surprised by the pushback here. I am not tying this to any
follow-up to CASSANDRA-15234, but to this work on its own merits. This epic
will be refactoring config, introducing new config, and all of this relates to
other existing config. These changes should all be thought of coherently, no?
> Guardrails for consistency levels
> ---------------------------------
>
> Key: CASSANDRA-17188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17188
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 4.x
>
>
> Add guardrails for read/write consistency levels, for example:
> {code:java}
> # Guardrail to warn about or reject read consistency levels.
> # By default all consistency levels are allowed.
> read_consistency_levels:
> warned: []
> disallowed: []
> # Guardrail to warn about or reject write consistency levels.
> # By default all consistency levels are allowed.
> write_consistency_levels:
> warned: []
> disallowed: []
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
