Alex Petrov commented on CASSANDRA-12373:

bq. Actually, we don't want to touch the schema.

Right. I've tried to fix my wording (you might have seen the edits), but it was 
still imprecise. 

Thank you for confirming the results format. I'm mostly done with {{SELECT}} 
special-casing, just need to run a bit more tests to make sure that all the 
cases are covered. Will move to adding {{2.x}} tests and then to 

bq. It would be really nice if we could keep all that code reasonably 
encapsulated too.

Gladly, most of time we just need a {{ResultSet}}, {{Partition}} and 
{{CFMetaData}}, so keeping this code aside should not be a big problem. We 
could do it similar to {{CompactTables}} class.

> 3.0 breaks CQL compatibility with super columns families
> --------------------------------------------------------
>                 Key: CASSANDRA-12373
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12373
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Sylvain Lebresne
>            Assignee: Alex Petrov
>             Fix For: 3.0.x, 3.x
> 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.

This message was sent by Atlassian JIRA

Reply via email to