There’s a chance it will fail to work - possible method signatures changed between 3.0 and 3.11. Try it in a test cluster before prod
-- Jeff Jirsa > On Nov 2, 2018, at 11:49 AM, Brian Spindler <brian.spind...@gmail.com> wrote: > > Nevermind, I spoke to quickly. I can change the cass version in the pom.xml > and re compile, thanks! > >> On Fri, Nov 2, 2018 at 2:38 PM Brian Spindler <brian.spind...@gmail.com> >> wrote: >> <image.png> >> >> >>> On Fri, Nov 2, 2018 at 2:34 PM Jeff Jirsa <jji...@gmail.com> wrote: >>> Easiest approach is to build the 3.11 jar from my repo, upgrade, then ALTER >>> table to use the official TWCS (org.apache.cassandra) jar >>> >>> Sorry for the headache. I hope I have a 3.11 branch for you. >>> >>> >>> -- >>> Jeff Jirsa >>> >>> >>>> On Nov 2, 2018, at 11:28 AM, Brian Spindler <brian.spind...@gmail.com> >>>> wrote: >>>> >>>> Hi all, we're planning an upgrade from 2.1.5->3.11.3 and currently we have >>>> several column families configured with twcs class >>>> 'com.jeffjirsa.cassandra.db.compaction.TimeWindowCompactionStrategy' and >>>> with 3.11.3 we need to set it to 'TimeWindowCompactionStrategy' >>>> >>>> Is that a safe operation? Will cassandra even start if the column family >>>> has a compaction strategy defined with a classname it cannot resolve? >>>> How to deal with different versioned nodes and different class names >>>> during the upgrade of the binaries throughout the cluster? >>>> >>>> Thank you for any guidance, >>>> Brian >>>>
