Cool, sounds fair enough. Thanks for the help, Rob! If anyone has upgraded from 1.1.X to 1.2.X, please feel invited to share any tips on issues you're encountered that are not yet documented.
Cheers, Paulo 2013/9/24 Robert Coli <rc...@eventbrite.com> > On Tue, Sep 24, 2013 at 1:41 PM, Paulo Motta <pauloricard...@gmail.com>wrote: > >> Doesn't the probability of something going wrong increases as the gap >> between the versions increase? So, using this reasoning, upgrading from >> 1.1.10 to 1.2.6 would have less chance of something going wrong then from >> 1.1.10 to 1.2.9 or 1.2.10. >> > > Sorta, but sorta not. > > https://github.com/apache/cassandra/blob/trunk/NEWS.txt > > Is the canonical source of concerns on upgrade. There are a few cases > where upgrading to the "root" of X.Y.Z creates issues that do not exist if > you upgrade to the "head" of that line. AFAIK there have been no cases > where upgrading to the "head" of a line (where that line is mature, like > 1.2.10) has created problems which would have been avoided by upgrading to > the "root" first. > > >> I'm hoping this reasoning is wrong and I can update directly from 1.1.10 >> to 1.2.10. :-) >> > > That's what I plan to do when we move to 1.2.X, FWIW. > > =Rob > -- Paulo Ricardo -- European Master in Distributed Computing*** Royal Institute of Technology - KTH * *Instituto Superior Técnico - IST* *http://paulormg.com*
