[
https://issues.apache.org/jira/browse/CASSANDRA-16733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362897#comment-17362897
]
Andres de la Peña commented on CASSANDRA-16733:
-----------------------------------------------
{quote}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.
{quote}
I think that the reason to keep the experimental features enabled in 3.0 and
3.x is that there could be code out there creating MVs or SASI indexes
automatically (original discussion
[here|https://lists.apache.org/thread.html/33666941e697af2d8097b9fd8c3b4301a727f8b7555dbbb544dc69a2%40%3Cdev.cassandra.apache.org%3E].
I'm not sure whether that could also be the case for a migration thing like
dropping compact storage, and I see dropping CS as more potentially harmful
than creating MVs/SASI, but I'd be happy keeping the same criteria for all
experimental features for the sake of consistency.
> 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/[email protected]/msg16789.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
