Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 12 Oct 2016 15:03:20 +0000 (UTC)
From: "Jeremiah Jordan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12994614.1470237400000.805552.1476284600479@Atlassian.JIRA>
In-Reply-To: <JIRA.12994614.1470237400000@Atlassian.JIRA>
References: <JIRA.12994614.1470237400000@Atlassian.JIRA> <JIRA.12994614.1470237400679@arcas>
Subject: [jira] [Commented] (CASSANDRA-12373) 3.0 breaks CQL compatibility
 with super columns families
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 12 Oct 2016 15:03:22 -0000


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

Jeremiah Jordan commented on CASSANDRA-12373:
---------------------------------------------

Don't forget the "snapshot" schema changing code.

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