[ 
https://issues.apache.org/jira/browse/CASSANDRA-17188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480200#comment-17480200
 ] 

Andres de la Peña commented on CASSANDRA-17188:
-----------------------------------------------

Guardrails fit in the current yaml in a way that is pretty similar to what was 
proposed in the CEP, with the only addition of nesting, which makes them 
identical to the already committed track_warnings. Besides, both features are 
disabled by default and their properties are commented. I don't know how well 
they fit into the new plans for the yaml, which don't have any associated CEP, 
ticket nor agreement. 

I don't know if the idea here is reverting any new property since 4.0 and block 
until we have that discussion, whenever we have it. In any case I don't see why 
this is exclusive to guardrails and not to all new properties since 4.0, since 
any new property should also fit in that holistic view for config that doesn't 
exist yet.

As for the difficulty of refactoring later, guardrails add an standard way to 
treat limits, so transforming existing properties that are suitable (and 
{{minimum_keyspace_rf}} might not be one of those) should make those properties 
much easier to adapt to whatever yaml format we use later. This is so because 
they have a common behaviour, validation rules, messaging formats, etc., so 
they are easy no modify all at once, and not one by one as it was needed in 
CASSANDRA-15234. So they put us closer to any planned future extensive changes 
in 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

Reply via email to