[
https://issues.apache.org/jira/browse/CASSANDRA-19532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835525#comment-17835525
]
Stefan Miklosovic commented on CASSANDRA-19532:
-----------------------------------------------
I think that this should be implemented as a new guardrail into existing
Guardrail framework we already have. This would be also very nicely
incorporated into CreateTriggerStatement.
Also, the benefit of using a guardrail is that it might be configured in
runtime via JMX so an admin can make her mind anytime whether trigger creation
/ execution is allowed or not. The way it is currently done, we basically need
to restart a node (and whole cluster) if we want to change it.
> Allow operators to disable the execution of triggers
> ----------------------------------------------------
>
> Key: CASSANDRA-19532
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19532
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Other
> Reporter: Abe Ratnofsky
> Assignee: Abe Ratnofsky
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, triggers are discouraged but there's no explicit way to disable
> them. Similar configuration already exists to disable other features, such as
> "conf.materialized_views_enabled". There should be a means for operators to
> gracefully disable the creation and execution of triggers.
>
> I have a patch ready for this, getting a first review now and will push it
> shortly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
