Support for Java 11 was added a long time ago, and it's been about 2 years
since it was released (Sept 2018). Had we released Cassandra 4 close to
that date, I'd be fine with keeping the status as experimental, but at this
point I'm wondering if releasing a new major version of C* that's primarily
> To those of you planning on moving to 4.0 soon after it's release, are you
> planning on deploying to JDK 11 or 8?
Curious, what's the harm in leaving it in experimental until 4.1/4.0.x ? I
thought we are emphasising putting in place a new precedence of Quality
First. The age, or stability, of
Thanks for bringing this up Jon! My current thinking is we should
officially support both 8 and 11. That increases the surface area we need
to test but I think its hard to predict what different users will run given
the current transition in the Java landscape.
Jordan
On Mon, Jul 13, 2020 at 11:4
Jon,
But Java 11 hasn't been tested in production. I would need to submit a patch
for documentation if Java 11 is made recommended version.
Based on a recent survey the majority are still using Java 8, probably because
it involves code review and update to migrate to a latter version.
"At 58%
Personally, I'd planned to upgrade to 4.0 on JDK8 but only wait a few weeks
before starting to update to JDK11 afterwards. Everything else we run's
been updated to JDK11, so the Cassandra clusters are the odd one out at
this point.
On Mon, Jul 13, 2020 at 12:19 PM Jordan West wrote:
> Thanks fo
All the major linux vendors are supporting JDK8 LTS (like 2024+ or
something) if I'm not mistaken, so I don't think there's a burning *need* to
push for JDK11 support specifically in 4.0. To Mick's point, no reason why
project folks that want JDK11 officially supported can't get started
working on
Link:
https://docs.google.com/document/d/1ktuBWpD2NLurB9PUvmbwGgrXsgnyU58koOseZAfaFBQ/edit#
Myself and a few other contributors are working with this point of view as
our frame of where we're going to work on improving testing on the project.
I figured it might be useful to foster collaboration m
JDK8 seems like the safe devil we know, but in the interest of trying to
gather a bit of data, I just posted a twitter poll.
https://twitter.com/patrickmcfadin/status/1282791302065557504?s=21
On Mon, Jul 13, 2020 at 12:26 PM Elliott Sims wrote:
> Personally, I'd planned to upgrade to 4.0 on JD
Can you please allow comments on the doc so we can leave feedback.
On Mon, Jul 13, 2020 at 2:16 PM Joshua McKenzie
wrote:
> Link:
>
> https://docs.google.com/document/d/1ktuBWpD2NLurB9PUvmbwGgrXsgnyU58koOseZAfaFBQ/edit#
>
>
> Myself and a few other contributors are working with this point of vie
>
> Can you please allow comments on the doc so we can leave feedback.
>
> Doc is view only; figured we could keep this to the ML.
>
That's a feature, not a bug.
Happy to chat here or on slack w/anyone. This is a complex topic so
long-form or high bandwidth communication is a better fit than gdo
We at Netflix have been testing 4.0 on Java 8, and we do not plan to
use Java 11 yet for C*, since we are, and for the considerable future will
be running Java 8 only in production.
On Mon, Jul 13, 2020 at 2:41 PM Patrick McFadin wrote:
> JDK8 seems like the safe devil we know, but in the intere
The majority of the testing that I'm doing and likely the people I
work with day to day tests 4.0 on Java 11, so we should gain some
experience over the next few months.
On Mon, Jul 13, 2020 at 5:27 PM Sumanth Pasupuleti
wrote:
>
> We at Netflix have been testing 4.0 on Java 8, and we do not plan
> On Jul 13, 2020, at 11:42 AM, Jon Haddad wrote:
>
> Support for Java 11 was added a long time ago, and it's been about 2 years
> since it was released (Sept 2018). Had we released Cassandra 4 close to
> that date, I'd be fine with keeping the status as experimental, but at this
> point I'm
13 matches
Mail list logo
