[
https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481084#comment-17481084
]
Benedict Elliott Smith commented on CASSANDRA-17188:
----------------------------------------------------
bq. The work done until now has gone through a CEP, mail list discussions and
multiple review processes involving multiple committers
It is quite explicit that the CEP process does not guarantee anything,
particularly if a concern was not previously recognised.
bq. 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?
I am asking that you propose a coherent approach for your configuration
changes, that takes into account existing conceptually related config,
particularly since you already plan to migrate many of these conceptually
related configs to guardrails (as noted in follow-up work). Since there is no
clear user-visible distinction between a guardrail imposed restriction and a
non-guardrail imposed restriction, some consideration should be given to how to
present these options to the user.
I am not proposing anything as draconian as reverting existing guardrails work,
only that you consider this now before committing further work on the epic.
This does not absolutely require engaging with other discussions about how to
refactor the rest of the yaml, or pausing work until that completes, although
that might overall be less burdensome for the project.
> 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]
