[
https://issues.apache.org/jira/browse/CASSANDRA-19532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835665#comment-17835665
]
Stefan Miklosovic commented on CASSANDRA-19532:
-----------------------------------------------
I was sleeping on it and I do not consider the second guardrail so important.
It is sad that we can not have two proper guardrails because of TCM replay and
config changes .... so if we were left with the second guardrail only, looking
into how similar features are turned on / off in cassandra.yaml, none of them
are guardrail enabled. For example, user defined functions or materialized
views or transient replication, dropping compact storage and similar. Also, I
think that the probability of somebody wanting to dynamically enable / disable
triggers in runtime is fairly minimal. I think that it is decided just once by
whole devops / engineering team if triggers are going to be used for a specific
deployment / project and these decisions are probably not changed frequently to
justify added complexity.
> 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: 1h 40m
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
