[
https://issues.apache.org/jira/browse/CASSANDRA-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178679#comment-16178679
]
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|https://github.com/apache/cassandra/commit/c510e001481637e1f74d9ad176f8dc3ab7ebd1e3].
Patch itself is committed to 3.0 with
[ce8c9b559f48e72cb4488e75211be338d28bdb13|https://github.com/apache/cassandra/commit/ce8c9b559f48e72cb4488e75211be338d28bdb13],
merged up to
[3.11|https://github.com/apache/cassandra/commit/4734ce7d94945126e40ec14c8eb2c305e768c6d1]
and
[trunk|https://github.com/apache/cassandra/commit/974d8fc099c0f426eea2440783b03e35c13fe528]
(trunk is merged with -s ours as agreed).
> 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.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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
