[
https://issues.apache.org/jira/browse/CASSANDRA-17147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451278#comment-17451278
]
David Capwell commented on CASSANDRA-17147:
-------------------------------------------
bq. We don't have a clear outcome for the discussion about that in the mail
list, although it seems that probably we are going in that direction
Thats my reading as well; there are some small concerns with nesting but most
are leaning towards nesting; the main talking point now is how deep and what
groupings. I am also planning to flesh out CASSANDRA-17166 once Ekaterina's
work gets merged, so would allow getter/setters, using camel case and have yaml
convert to snake, and support "." notation for nested configs.
bq. I think our main concern at this point is the nested yaml config
As long as we are not releasing 4.1 soon, we can also prob go with "every
commit can break the yaml" until the epic is fully closed; so can prob move
forward even though the email thread isn't fully complete.
bq. I'll try to get ready a version of the patch with nested config, even if we
miss some of the ongoing config improvements.
works for me.
> Guardrails prototype
> --------------------
>
> Key: CASSANDRA-17147
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17147
> 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
>
> Time Spent: 14h 50m
> Remaining Estimate: 0h
>
> The purpose of this ticket is creating an initial implementation of the
> guardrails framework, as well as adding a few simple guardrails using this
> framework.
> To keep things easy, this initial implementation would only support
> guardrails that are triggered on the coordinator, and they would be
> dynamically updatable only through JMX.
> Once we have this initial framework ready in a feature branch we can have
> multiple tickets addressing all the things that would have been left out of
> the scope of this ticket, such as:
> * Dynamic updates through virtual tables
> * Being able to notify about guardrails triggered on replicas
> * Using custom exceptions other than {{InvalidRequestException}}.
> * Porting existing limits to use the new guardrails framework
> * Adding new guardrails beyond the initial ones
> The reason for having this simpler prototype is that it will give us a common
> ground to parallelize work on the parts mentioned above.
--
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
