[
https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480166#comment-17480166
]
Caleb Rackliffe edited comment on CASSANDRA-17188 at 1/21/22, 4:24 PM:
-----------------------------------------------------------------------
[~benedict] Aside from this, I still think we (more than happy to do it myself)
should create a new Jira that _does_ start to socialize our overall proposal(s)
for the config as soon as CASSANDRA-15234 merges. Even if we intend for that to
be a 5.0 item, it can inform the guardrails/limits work here before it gets
release in 4.1, which is the worry I'm sure you and I both have around this.
was (Author: maedhroz):
[~benedict] Aside from this, I still think we (more than happy to do it myself)
should create a new Jira that _does_ start to socialize our overall proposal(s)
for the config as soon as CASSANDRA-15234 merges, even if we intend for that to
be a 5.0 item.
> 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
