+1. IMO there’s very little reason to use 3.0 at this point. If someone wants to back port and make a 3.0 patch publicly available, cool, but merging it into 3.0 after 2 years doesn’t make much sense to me.
> On Jul 31, 2017, at 9:26 AM, Jeremiah D Jordan <jeremiah.jor...@gmail.com> > wrote: > > >> On Jul 31, 2017, at 12:17 PM, Jeff Jirsa <jji...@apache.org> wrote: >> On 2017-07-29 10:02 (-0700), Jay Zhuang <jay.zhu...@yahoo.com.INVALID> >> wrote: >>> Should we consider back-porting it to 3.0 for the community? I think >>> this is a performance regression instead of new feature. And we have the >>> feature in 2.1, 2.2. >>> >> >> Personally / individually, I'd much rather see 3.0 stabilize. > > +1. The feature is there in 3.11.x if you are running one of the use cases > where this helps, and for most existing things 3.0 and 3.11 are about the > same stability, so you can go to 3.11.x if you want to keep using the off > heap stuff. > > -Jeremiah > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
