cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-12373) 3.0 breaks CQL compatibility with super columns families
Date Mon, 28 Nov 2016 08:05:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604830#comment-15604830
] 

Alex Petrov edited comment on CASSANDRA-12373 at 11/28/16 8:05 AM:
-------------------------------------------------------------------

I hope I've covered all the corner cases. A small note on the implementation: currently I'm
using hardcoded column names {{column2}} and {{value}} for the fake columns. If you think
that can lead to some sort of collision or problem, we can try relying on column name generation
from {{CompactTables}}, although it's going to be more or less same. These columns are not
persisted together with the rest of schema, they're completely virtual and created during
{{CFMetadata}} construction.

As [~slebresne] mentioned, {{SelectStatement}}, {{UpdateStatement}} and {{DeleteStatement}}
were modified to special-case supercolumns, converting from map to two columns and reverse.

|[trunk|https://github.com/ifesdjeen/cassandra/tree/12373-trunk-squashed]|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-trunk-squashed-dtest/]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-trunk-squashed-testall/]|
|[3.X|https://github.com/ifesdjeen/cassandra/tree/12373-3.X-squashed]|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-3.X-squashed-dtest/]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-3.X-squashed-testall/]|
|[2.2|https://github.com/ifesdjeen/cassandra/tree/12373-2.2-squashed]|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-2.2-squashed-dtest/]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-2.2-squashed-testall/]|
|[dtest patch|https://github.com/ifesdjeen/cassandra-dtest/tree/12373]|


was (Author: ifesdjeen):
I hope I've covered all the corner cases. A small note on the implementation: currently I'm
using hardcoded column names {{column2}} and {{value}} for the fake columns. If you think
that can lead to some sort of collision or problem, we can try relying on column name generation
from {{CompactTables}}, although it's going to be more or less same. These columns are not
persisted together with the rest of schema, they're completely virtual and created during
{{CFMetadata}} construction.

As [~slebresne] mentioned, {{SelectStatement}}, {{UpdateStatement}} and {{DeleteStatement}}
were modified to special-case supercolumns, converting from map to two columns and reverse.

|[trunk|https://github.com/ifesdjeen/cassandra/tree/12373-trunk-squashed-2]|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-trunk-squashed-2-dtest/]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-trunk-squashed-2-testall/]|
|[2.2|https://github.com/ifesdjeen/cassandra/tree/12373-2.2-squashed]|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-2.2-squashed-dtest/]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-12373-2.2-squashed-testall/]|
|[dtest patch|https://github.com/ifesdjeen/cassandra-dtest/tree/12373]|

> 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)

Mime
View raw message