[
https://issues.apache.org/jira/browse/CASSANDRA-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608436#comment-15608436
]
Alex Petrov edited comment on CASSANDRA-12373 at 10/26/16 1:20 PM:
-------------------------------------------------------------------
I've added a possible fix for that. In order to allow column renames, we have
to change {{LegacySchemaMigrator}} to pass the columns from older versions in
case of supercolumn family. In 3.0, however, they're removed from
{{clustering}} and {{regular}} and converted back to fake "virtual" columns
(with corresponding {{KIND}} and name, in order to avoid them popping up in
queries. Already upgraded tables will still work, even though their schema
doesn't have the second clustering and compact value columns, as they're
initialised as fake columns if missing.
was (Author: ifesdjeen):
I've added a possible fix for that. In order to allow column renames, we have
to change {{LegacySchemaMigrator}} to pass the columns from older versions in
case of supercolumn family. In 3.0, however, they're removed from
{{clustering}} and {{regular}} and converted back to fake "virtual" columns
(with corresponding {{KIND}} and name, in order to avoid them popping up in
queries. Already upgraded tables will still work, even though their schema
doesn't have the second clustering and compact value columns, as they're added
if missing.
> 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
(v6.3.4#6332)
