[CASSANDRA-12373] 3.0 breaks CQL compatibility with super columns families

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.15, 3.11.1, 4.0-alpha1, 4.0
• Component/s: Legacy/CQL
• Bug Category: Correctness - API / Semantic Implementation
• Severity: Normal
• Assignee: Alex Petrov
• Reporter: Sylvain Lebresne

Authors

Alex Petrov

Reviewers

Sylvain Lebresne

• Created: 03/Aug/16 15:16
• Updated: 15/May/20 08:00
• Resolved: 25/Sep/17 11:15

Description

This is a follow-up to CASSANDRA-12335 to fix the CQL side of super column compatibility.

The details and a proposed solution can be found in the comments of CASSANDRA-12335 but the crux of the issue is that super column famillies show up differently in CQL in 3.0.x/3.x compared to 2.x, hence breaking backward compatibilty.

Issue Links

• is depended upon by: CASSANDRA-10857 Allow dropping COMPACT STORAGE flag from tables in 3.X