[ 
https://issues.apache.org/jira/browse/CASSANDRA-16733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Lerer updated CASSANDRA-16733:
---------------------------------------
          Fix Version/s:     (was: 4.0-rc)
                             (was: 3.11.x)
                             (was: 3.0.x)
                         4.0
                         3.11.11
                         3.0.25
          Since Version: 3.0.16
    Source Control Link: 
https://github.com/apache/cassandra/commit/9b6dd382bdf4a71c06091736ff98cb1307ff0e97
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Committed into 3.0 at 9b6dd382bdf4a71c06091736ff98cb1307ff0e97 and merged into 
3.11, 4.0.0, 4.0 and trunk 

> 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: 3.0.25, 3.11.11, 4.0-rc2, 4.0
>
>          Time Spent: 1h
>  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