cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9930) Ability to skip a major version while upgrading
Date Wed, 29 Jul 2015 20:44:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646734#comment-14646734
] 

Aleksey Yeschenko commented on CASSANDRA-9930:
----------------------------------------------

With 3.X, what we've been promising *so far* is to treat the increments as we are treating
minors now. You should be able to jump from 3.1 to 3.12 directly.

Not sure if 3.0 -> 3.1 is something we *must* support. We will probably want to drop a
whole lot of compatibility luggage that had been added for CASSANDRA-8099 sake (a lot).

2.1 to 3.0, that we should definitely support, though - there is just no good reason not to,
given how close 2.1 and 2.2 are. The benefits outweigh the hassles of extra testing.

> Ability to skip a major version while upgrading
> -----------------------------------------------
>
>                 Key: CASSANDRA-9930
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9930
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Ryan McGuire
>             Fix For: 3.0.0 rc1
>
>
> Once we move to a [tick-tock model|http://www.mail-archive.com/dev%40cassandra.apache.org/msg07771.html]
we will need the ability to upgrade from stable release to stable release, skipping a single
version in the process.
> Example: 3.0 -> 3.2 (skipping the pass-through upgrade to 3.1 we normally have to
do)
> I would recommend we code this so that we can upgrade 2.1 directly to 3.0 as well, it's
probably too much work to do this for versions prior to that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message