[ https://issues.apache.org/jira/browse/CASSANDRA-16048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196777#comment-17196777 ]
Alex Petrov commented on CASSANDRA-16048: ----------------------------------------- [~jwest] missed your comment about Harry. We do have Harry for this; and it would correctly find this inconsistency. However, schema changes are not propagated throughout the cluster in a deterministic way, so we'd have to accept both responses until we can guarantee that {{DROP COMPACT STORAGE}} has propagated. For now, I think, the best way to proceed with this would be to populate a table, drop compact storage, wait for schema convergence, and re-validate it with a new schema. But in the future we'll definitely have some better support for schema changes. > Safely Ignore Compact Storage Tables Where Users Have Defined Clustering and > Value Columns > ------------------------------------------------------------------------------------------ > > Key: CASSANDRA-16048 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16048 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL > Reporter: Jordan West > Assignee: Jordan West > Priority: Normal > Fix For: 4.0-beta > > > Some compact storage tables, specifically those where the user has defined > both at least one clustering and the value column, can be safely handled in > 4.0 because besides the DENSE flag they are not materially different post 3.0 > and there is no visible change to the user facing schema after dropping > compact storage. We can detect this case and allow these tables to silently > drop the DENSE flag while still throwing a start-up error for COMPACT STORAGE > tables that don’t meet the criteria. -- 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