[
https://issues.apache.org/jira/browse/CASSANDRA-12716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544726#comment-15544726
]
Sylvain Lebresne commented on CASSANDRA-12716:
----------------------------------------------
I should note that the patch is currently breaking cqlsh because it seems the
python driver currently use still tries to read the old
{{system.schema_keyspaces}} table, which doesn't exist anymore. Which is tad
surprising in that reading those is wrong on 3.0 already but I don't know a
whole lot more. It could be fixed on the last versions of the python driver,
but I'm not sure what is the blessed procedure to build the
{{cassandra-driver-internal-only}} zip we use for cqlsh, so haven't tried.
Would appreciate the insights from the experts on cqlsh and the python driver
(cc [~Stefania], [~aholmber]?)
> Remove pre-3.0 compatibility code for 4.0
> -----------------------------------------
>
> Key: CASSANDRA-12716
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12716
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 4.0
>
>
> CASSANDRA-8099 make subsequent changes to internal formats so that we have
> quite a bit of backward compatibility code a bit over the place. Due to that,
> but also as a natural evolution, I believe we always had a tacit agreement
> that 3.0/3.X would be a mandatory step on the upgrade to 4.X, so that we can
> remove pre-3.0 compatibility (that is, we won't support going from any 2.x
> release directly to 4.0, you'll have to upgrade to at least some 3.0 release
> first).
> I think it's time to create the 4.0 branch and remove that pre-3.0 backward
> compatibility code, which should clean code quite a bit, and that's the goal
> of this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
