[ https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482533#comment-17482533 ]
Andres de la Peña commented on CASSANDRA-17188: ----------------------------------------------- {quote} 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. {quote} What currently identifies a limit as a guardrail is that it's an optional safety limit that is triggered exclusively by queries of ordinary users. They can be globally and/or individually disabled, and they don't affect superusers nor internal queries. In the future we might move in different directions and use them for asynchronous background processes such as compaction, or perhaps adapt them to be used on every limit defined in a future configuration, but we are not there yet. I understand that we should discuss whether current config properties should be migrated to guardrails or not, and we can do that in the tickets for migrating existing properties. However, this particular guardrail doesn't migrate any existing property, nor seems inconsistent with what is currently in the yaml. > 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