[
https://issues.apache.org/jira/browse/CASSANDRA-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15585042#comment-15585042
]
Alex Petrov edited comment on CASSANDRA-12373 at 10/18/16 11:53 AM:
--------------------------------------------------------------------
[~slebresne] [~iamaleksey] do we want to also support filtering on {{column2}}
and {{value}} for supercolumns? In {{2.x}} it wasn't supported (predicate on
non-2i column).
Also, do we want to support things like materialized views and group by? Or we
just want a basic read support so that people could migrate from this table
type?
was (Author: ifesdjeen):
[~slebresne] [~iamaleksey] do we want to also support filtering on {{column2}}
and {{value}} for supercolumns? In {{2.x}} it wasn't supported (predicate on
non-2i column).
Also, do we want to support aggregates (like {{max}} etc), materialized views
and group by? Or we just want a basic read support so that people could migrate
from this table type?
> 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)
