You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2022/01/24 17:31:00 UTC
[jira] [Comment Edited] (CASSANDRA-17148) Adapt track_warnings to Guardrails
[ https://issues.apache.org/jira/browse/CASSANDRA-17148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481271#comment-17481271 ]
David Capwell edited comment on CASSANDRA-17148 at 1/24/22, 5:30 PM:
---------------------------------------------------------------------
I am cool moving configs under guardrails to be consistent, I agree this work should be a different ticket, either a subtask or new JIRA.
was (Author: dcapwell):
I am cool moving configs under guardrails to be consistent, but can we make a subtask or new JIRA to track that work? Would be good for 1 commit = 1 jira IMO
> Adapt track_warnings to Guardrails
> ----------------------------------
>
> Key: CASSANDRA-17148
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17148
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
>
> The purpose of this ticket is adapting the warnings added by CASSANDRA-16850 to use the new Guardrails framework. This will involve extending the framework to be able to propagate warnings and failures triggered on replicas, taking advantage of the machinery added in that ticket.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org