You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jordan West (Jira)" <ji...@apache.org> on 2020/08/13 22:29:00 UTC
[jira] [Updated] (CASSANDRA-16048) Safely Ignore Compact Storage
Tables Where Users Have Defined Clustering and Value Columns
[ https://issues.apache.org/jira/browse/CASSANDRA-16048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jordan West updated CASSANDRA-16048:
------------------------------------
Change Category: Operability
Complexity: Normal
Component/s: Legacy/CQL
Status: Open (was: Triage Needed)
We can do this before or after CASSANDRA-13994 but I think its better to wait until after that patch merges to prevent anyone from having to rebase.
> 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
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org