cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12373) 3.0 breaks CQL compatibility with super columns families
Date Thu, 20 Oct 2016 15:06:58 GMT


Aleksey Yeschenko commented on CASSANDRA-12373:

bq. Should we include support for filtering, LWTs and materialized views?

The minimal requirement is to have the functionality present in 2.1.x/2.2.x restored - for
people who migrated their supercolumn-using apps from Thrift to CQL and might already be using
certain CQL features with those tables in their code. MVs weren't part of it, LWT and filtering
- not sure.

> 3.0 breaks CQL compatibility with super columns families
> --------------------------------------------------------
>                 Key: CASSANDRA-12373
>                 URL:
>             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

View raw message