[ https://issues.apache.org/jira/browse/CASSANDRA-16733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363085#comment-17363085 ]
Andres de la Peña commented on CASSANDRA-16733: ----------------------------------------------- The last commit setting {{enable_drop_compact_storage}} as false by default in 3.0 and 3.11 looks good to me, +1 if CI is ok. > 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: 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