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

Benjamin Lerer commented on CASSANDRA-16733:
--------------------------------------------

Regarding the flag default. I simply followed what we did so far for all the 
other experimental features. Kept the flag to {{true}} for released versions. 
For MVs for example: it is {{true}} in 
[3.0|https://github.com/apache/cassandra/blob/cassandra-3.0/conf/cassandra.yaml#L990]
 and 
[3.11|https://github.com/apache/cassandra/blob/cassandra-3.11/conf/cassandra.yaml#L1276],
 but {{false}} in 
[4.0|https://github.com/apache/cassandra/blob/cassandra-4.0/conf/cassandra.yaml#L1428].
 The same logic is used for SASI. 

> Allow operators to disable 'ALTER ... DROP COMPACT STORAGE' statements
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-16733
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16733
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/CQL
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>            Priority: Normal
>             Fix For: 4.0-rc2, 3.0.x, 3.11.x, 4.0-rc
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> {{ALTER ... DROP COMPACT STORAGE}} statements have not been extensively 
> tested and suffer from several issues like:
> * As COMPACT tables did not have primary key liveness there empty rows
> inserted AFTER the ALTER will be returned whereas the one inserted before
> the ALTER will not.
> * Also due to the lack of primary key liveness the amount of SSTables being
> read will increase resulting in slower queries (CASSANDRA-16675)
> * After DROP COMPACT it becomes possible to ALTER the table in a way that
> makes all the row disappears
> * There is a loss of functionality around null clustering when dropping
> compact storage (CASSANDRA-16069)
> To avoid running into those issues this ticket will introduce a new flag that 
> allow operators to disable those statements on their clusters.
> see https://www.mail-archive.com/dev@cassandra.apache.org/msg16789.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to