[ 
https://issues.apache.org/jira/browse/CASSANDRA-17495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17520712#comment-17520712
 ] 

Josh McKenzie commented on CASSANDRA-17495:
-------------------------------------------

Rebased w/the other guardrails tickets that have gone in recently; fresh CI 
running here:

[JDK8 
CI|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/210/workflows/a75a6ff2-4416-4106-ac5e-a0b9b1c2b47d]
[JDK11 
CI|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/210/workflows/d0e55393-e760-45e0-a65d-7b48feb052fd]

> 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

Reply via email to