[
https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481054#comment-17481054
]
Andres de la Peña commented on CASSANDRA-17188:
-----------------------------------------------
The work done until now has gone through a CEP, mail list discussions and
multiple review processes involving multiple committers, and it has been done
without conflicting with CASSANDRA-15234. This particular ticket just adds some
new properties that are in line with already committed work, and doesn't change
anything of the current yaml.
I don't see what planned near-term work guardrails and track warnings are
inconsistent with, since as far as I know we don't have any agreement on how a
new config organization would like.
Is your proposal to revert guardrails and track warnings, or just stop all new
work on these until we get to an agreement on some different organization of
the yaml? If that's the case, would this revert or freeze affect any of the
other properties that have been added to the yaml since the last release?
> 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: [email protected]
For additional commands, e-mail: [email protected]
