[
https://issues.apache.org/jira/browse/CASSANDRA-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094434#comment-16094434
]
Alex Petrov commented on CASSANDRA-12373:
-----------------------------------------
Rebased on top of {{3.0}} and {{3.11}}. Since we're doing this patch in the
preparation for 4.0 where there'll be no thrift, supercolumnfamiles or compact
tables, we do not need a trunk patch (only removing last bits of
supercolumnfamilies and compact tables from code if there are any).
|[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...ifesdjeen:12373-3.0]|[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...ifesdjeen:12373-3.11]|[dtest|https://github.com/riptano/cassandra-dtest/compare/master...ifesdjeen:12373]|
{{3.0}} and {{3.11}} patches are quite similar but not exactly the same. In 3.0
there are fewer tests (due to the missing features) and there was a difference
in {{SelectStatement}} since {{processPartitions}} is called from two places
there. Not sure if we needed to abstract/hide it.
CI results, including upgrade tests look good.
> 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: [email protected]
For additional commands, e-mail: [email protected]
