[
https://issues.apache.org/jira/browse/CASSANDRA-17495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514798#comment-17514798
]
Josh McKenzie commented on CASSANDRA-17495:
-------------------------------------------
Having a single knob to remove dangerous functionality from your userbase is
superior to having a N step process where N is your number of users in my
opinion.
This is similar to the ticket about secondary indexes, where we *can* do it
with the existing mechanisms, but it's more onerous for operators, more
brittle, more prone to error, and more prone to "leakage" (in this case,
someone creating a new user, forgetting to add the role w/the revoked
permissions to that user, and then that user circumventing the intended feature
blockage).
> Add Guardrail for ALTER TABLE ADD / DROP / RENAME columns
> ---------------------------------------------------------
>
> Key: CASSANDRA-17495
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17495
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.x
>
>
> Operators should have the ability to freeze the schema of tables in place so
> users can't mutate columns during various cluster operations. For an example
> of some of the risks see CASSANDRA-13004.
--
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
