cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12373) 3.0 breaks CQL compatibility with super columns families
Date Mon, 25 Sep 2017 07:47:00 GMT


Alex Petrov commented on CASSANDRA-12373:

Thank you for the thorough review & patience [~slebresne], great job on your side. 

Compatibility tests are committed to 2.2 with [c510e001481637e1f74d9ad176f8dc3ab7ebd1e3|].

Patch itself is committed to 3.0 with [ce8c9b559f48e72cb4488e75211be338d28bdb13|],
merged up to [3.11|]
and [trunk|]
(trunk is merged with -s ours as agreed).

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message