[
https://issues.apache.org/jira/browse/CASSANDRA-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137056#comment-16137056
]
Jeremiah Jordan commented on CASSANDRA-12373:
---------------------------------------------
bq. I'll note at this point that the "why" this is done this way is unimportant
here, we are way way past changing any of this. This is how things work in 2.x
however and the only goal here is to make it work the same way in 3.x so user
can upgrade without problems.
I agree we need to expose these the same way in 3.x, but one thing to remember
is that in 2.x non SCF tables worked the same way, but in 3.x we started
exposing the defined columns as "static" and the undefined ones as
column1/value. Is there a similar way to expose all the data for SCF?
> 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.11.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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
