You could also pull TWCS out of the version of Cassandra you want to deploy, fix the imports and change the package name. Then you've got the same version as OSS, just under the name you're using in 2.1. Once you've moved to 3.11, you can switch to the OSS version.
On Thu, Jul 9, 2020 at 9:09 AM Gil Ganz <gilg...@gmail.com> wrote: > Great, thank you very much! > > On Thu, Jul 9, 2020 at 7:02 PM Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > >> On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz <gilg...@gmail.com> wrote: >> >>> That sounds very interesting Alex, so just to be sure I understand, it >>> was like this >>> 1 - you had 2.1 cluster running with the 2.1 version jar >>> 2 - you upgraded to 3.0, starting the cluster with the 3.0 version jar >>> that has the same strategy name >>> 3 - you changed the compaction strategy to use the built in one? >>> >> >> Correct. >> >> Another question, did changing the compaction strategy from one twcs to >>> the other trigger merging of old sstables? >>> >> >> I don't recall any unexpected action from changing the strategy, but of >> course you should verify on a test system first if you have one. >> >> Cheers, >> -- >> Alex >> >>
