[
https://issues.apache.org/jira/browse/CASSANDRA-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130721#comment-17130721
]
Sylvain Lebresne commented on CASSANDRA-13994:
----------------------------------------------
{quote}please don't remove it this far into the alphas.
{quote}
{quote}removing protocol V3 at this point would delay the ability of many to
upgrade to Cassandra 4.0
{quote}
Fair enough, I don't mind keeping it more than that.
Though, fwiw, I do am a bit surprised by your points. Protocol v4 was added
back in 2.2.0, and was a small enough iteration over V3 that the main drivers
supported it right away. And C* 4.0 does not support upgrading from 2.X
directly at all (in fact, reminder that you need to upgrade from at least
3.0.13 or 3.11.0 according to the NEWS file). Requiring that users have
upgraded their driver version in the last 5 years didn't felt, a priori, a big
constraining ask to me. But I trust your "lots of people" and "of many" are
backed by data, so again, happy to keep V3, I just admit surprise. TIL.
> Remove COMPACT STORAGE internals before 4.0 release
> ---------------------------------------------------
>
> Key: CASSANDRA-13994
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13994
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Local Write-Read Paths
> Reporter: Alex Petrov
> Assignee: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.0, 4.0-rc
>
>
> 4.0 comes without thrift (after [CASSANDRA-11115]) and COMPACT STORAGE (after
> [CASSANDRA-10857]), and since Compact Storage flags are now disabled, all of
> the related functionality is useless.
> There are still some things to consider:
> 1. One of the system tables (built indexes) was compact. For now, we just
> added {{value}} column to it to make sure it's backwards-compatible, but we
> might want to make sure it's just a "normal" table and doesn't have redundant
> columns.
> 2. Compact Tables were building indexes in {{KEYS}} mode. Removing it is
> trivial, but this would mean that all built indexes will be defunct. We could
> log a warning for now and ask users to migrate off those for now and
> completely remove it from future releases. It's just a couple of classes
> though.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
