2.2 is particularly hard because of the major storage format changes that took place.
I think if we want to retain (restore) upgrade support from 3.x I would support that, but 2.x is probably too burdensome and likely to have too many hard edges. I think if users only had to upgrade 2.2->3.x then eg 3.x->6.0 that would be a pretty friendly upgrade path all things considered. > On 11 Dec 2024, at 12:03, Miklosovic, Stefan via dev > <dev@cassandra.apache.org> wrote: > > Hey, > > I want to fork the thread where we are mentioning that 2.2 -> 5.0 would be > cool to support. > > I was involved in checking that offline upgrades from 3.0 to 5.0 work and > fixed few issues along the way (1), hence I can imagine that supporting 2.2 > -> 5.0 would be basically the same thing just on steroids and more involved? > Anyway, having a stab into this is not useless at all, I will at least go > deep into the upgrade stuff I have never given a lot of thought to which is > good learning experience. > > Any tips where to start? Was any progress done by anybody already in this > matter to not start from zero? > > (1) https://issues.apache.org/jira/browse/CASSANDRA-19002 > > Regards
