After an upgrade I recommend running upgrade sstables no matter what the
version change is. If it's not needed, nothing will happen.
On Fri, Oct 13, 2017 at 4:30 AM Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:
> And extremely useful/important in the field not being a strict requi
And extremely useful/important in the field not being a strict requirement
immediately upgrading sstables, especially for not closely monitored
environments, e.g. unattended deployments like development machines or even
customer on-prem installations etc.
Cassandra's data backwards compatibilit
Old restrictions that have been lifted Jeff :)
Ever since 2.0 we have supported streaming old sstables, see here for the 2.0
ticket:
https://issues.apache.org/jira/browse/CASSANDRA-5772
That was broken in early 3.0, but had since been fixed by the ticket Marcus
linked https://issues.apache.org/j
Same here, regarding sincere question to know the corner cases from 2.1 =>
3.11.1, but Marcus already provided the JIRA ticket.
Thanks!
-Original Message-
From: Per Otterström [mailto:per.otterst...@ericsson.com]
Sent: Freitag, 13. Oktober 2017 09:01
To: dev@cassandra.apache.org
Subject
https://issues.apache.org/jira/browse/CASSANDRA-10990
On Fri, Oct 13, 2017 at 9:00 AM, Per Otterström wrote:
> Hepp!
>
> Just to be clear, I'm not claiming this to be the case, it is a sincere
> question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm
> asking. Some initial test
Hepp!
Just to be clear, I'm not claiming this to be the case, it is a sincere
question. My team is planning an upgrade from 2.2 to 3.0 which is why I'm
asking. Some initial tests indicate that repairs etc work well before running
upgradesstables (assuming all nodes are upgraded to 3.0). But if
