On Fri, 13 Dec 2024 at 06:06, Jeremiah Jordan <jeremiah.jor...@gmail.com> wrote:
> TL;DR - in progress migration off 2.2 to 5.0 is annoying as there were >>> different bugs in the past we have to support again. Out of process >>> migration to me feels far more plausible, but feels annoying without >>> splitting off our reader/writer… doable… just more annoying… >> >> > This is your main blocker for the 5.0/trunk code converting 2.2 sstables > correctly. You would have to bring back a bunch of code paths special > casing those versions and dealing with bugs in them. If you are actually > interested in figuring out an offline 2.2 to 5.0 path I would recommend you > do it in two steps. Offline 2.2 to 4.1? or what ever the latest thing is > that can sstableupgrade a 2.2 sstable, and then offline the result of that > with 5.0. But at that point maybe you just do it online in those two steps. > Stepping through safe upgrade edges is currently a requirement, and I suspect will often have value. Something like `nodetool sstableupgrade --step 3.0,4.1,5.0` would be useful. While it would take longer to do offline upgrades, it allows us to maintain simpler code, and draw the lineations when we must.
