Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B8E1D200BBB for ; Wed, 26 Oct 2016 15:21:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B7B25160ACA; Wed, 26 Oct 2016 13:21:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0F878160AFD for ; Wed, 26 Oct 2016 15:20:59 +0200 (CEST) Received: (qmail 84616 invoked by uid 500); 26 Oct 2016 13:20:59 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 84561 invoked by uid 99); 26 Oct 2016 13:20:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2016 13:20:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AC5B42C2ABA for ; Wed, 26 Oct 2016 13:20:58 +0000 (UTC) Date: Wed, 26 Oct 2016 13:20:58 +0000 (UTC) From: "Alex Petrov (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 26 Oct 2016 13:21:00 -0000 [ 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)