Re: [DISCUSS] Revisiting Java 11's experimental status

Another interesting data point from our site: https://cassandra.apache.org/doc/latest/new/java11.html?highlight=support Support Matrix The support matrix for the Java versions for compiling and running

Re: [DISCUSS] Revisiting Java 11's experimental status

Should clarify - not saying automated tests are enough. Thinking we should articulate better what supported means (all tools work, etc - manually checking the swath of stuff that’s lacking automated testing assuming we even have a good idea of that scope). If we’re committing to all automated

Re: [DISCUSS] Revisiting Java 11's experimental status

> > This stance does not mean that java 11 testing is on-par with our > java 8 testing, it only means we treat reports of issues equality > regardless of JDK version. Outside our automated testing suites, what other testing as a project community do we consider necessary to dub something

Re: [DISCUSS] Revisiting Java 11's experimental status

This makes sense to me. A bug is a bug regardless of the JVM that exposes it. Java 11 still considered experimental. Users should understand they are on the less trodden path when using it. -Jeremiah > On Aug 19, 2020, at 7:36 PM, David Capwell wrote: >

Re: [DISCUSS] Revisiting Java 11's experimental status

> > s/ignore/defer until after 4.0 GA/g (semantic difference that may not sway > you) Even if it is experimental, I feel that it would be best for users if we treat java 11 bug reports the same as java 8 bug reports; it would be a bad user experience if a user found out we knew about an issue

Re: [DISCUSS] Revisiting Java 11's experimental status

> > java 11 is experimental, so lets ignore issue X s/ignore/defer until after 4.0 GA/g (semantic difference that may not sway you) If we block the release on JDK11 issues we find, it *seems* to me that that's the same as saying "JDK11 is supported" assuming we have the same a) level of testing

Re: [DISCUSS] Revisiting Java 11's experimental status

My statement was more coming from the fact that if we test on java 8 and find an issue it is a release blocker, so saying java 11 should be treated with the same regard as java 8 when it comes to filing/fixing issues; when it comes to filing and fixing issues, we shouldn't have different stances

Re: [DISCUSS] Revisiting Java 11's experimental status

> > 3) during 4.0 qualification, issues found on jdk 11 should block the > release Maybe we let 2 run and see how many issues there are before we call release blocking? On Tue, Aug 18, 2020 at 10:05 PM David Capwell wrote: > I would propose the following: > > 1) leave jdk 11 marked as

Re: [DISCUSS] Revisiting Java 11's experimental status

I would propose the following: 1) leave jdk 11 marked as experimental 2) make sure CI runs jdk 8 and jdk 11 for all builds (circle / jenkins) 3) during 4.0 qualification, issues found on jdk 11 should block the release This should get us in good shape to potentially be ready to flip the switch

Re: [DISCUSS] Revisiting Java 11's experimental status

Where did we land on this? Don't seem to have a clear consensus from thread discussion. On Mon, Jul 20, 2020 at 10:02 PM Deepak Vohra wrote: > The same link was posted earlier also. > For Java 8 and 11 the poll result is very similar. > Java 8 =58.4%Java 11 =22.56% > > > On Monday, July

Re: [DISCUSS] Revisiting Java 11's experimental status

Got it, thanks for the correction. On Mon, Jul 20, 2020 at 4:28 PM Brandon Williams wrote: > I believe you can run them on 11, but you can't build them on it. > > On Mon, Jul 20, 2020 at 6:11 PM Jeff Jirsa wrote: > > > > I still dont get it, because you can't use any released version of > >

Re: [DISCUSS] Revisiting Java 11's experimental status

I believe you can run them on 11, but you can't build them on it. On Mon, Jul 20, 2020 at 6:11 PM Jeff Jirsa wrote: > > I still dont get it, because you can't use any released version of > cassandra with anything other than jdk8. > > > > On Mon, Jul 20, 2020 at 2:50 PM Patrick McFadin wrote: >

Re: [DISCUSS] Revisiting Java 11's experimental status

I still dont get it, because you can't use any released version of cassandra with anything other than jdk8. On Mon, Jul 20, 2020 at 2:50 PM Patrick McFadin wrote: > Follow-up on the informal poll I did on twitter: > https://twitter.com/patrickmcfadin/status/1282791302065557504?s=21 > >

Re: [DISCUSS] Revisiting Java 11's experimental status

Follow-up on the informal poll I did on twitter: https://twitter.com/patrickmcfadin/status/1282791302065557504?s=21 Offered up as data to be used as you will. 161 votes <= JDK8: 59% JDK9 or 10: 7% JDK11 or 12: 27% JDK13 or 14: 7% On Wed, Jul 15, 2020 at 3:19 AM Robert Stupp wrote: > Yea,

Re: [DISCUSS] Revisiting Java 11's experimental status

Yea, ZGC is kinda tricky in 11. — Robert Stupp @snazy > On 14. Jul 2020, at 15:02, Jeff Jirsa wrote: > > Zgc > >> On Jul 14, 2020, at 2:26 AM, Robert Stupp wrote: >> >>  >>> On 14. Jul 2020, at 07:33, Jeff Jirsa wrote: >>> >>> Perhaps the most notable parts of jdk11 (for cassandra)

Re: [DISCUSS] Revisiting Java 11's experimental status

I think we should start getting automated testing to use java 11 in 4.0, but that stability on 4.0 should not be a blocker for 4.0. Mick is doing a lot of work to get builds running with java 11 (see https://issues.apache.org/jira/browse/CASSANDRA-15809) and a lot more work is needed to get java

Re: [DISCUSS] Revisiting Java 11's experimental status

My goal here was to collect information, specifically around what people's needs are and what people are testing. Some teams have a mandate they need to move to Java 11, Python 3, etc. Some just want to take advantage of features like low overhead heap profiling [1]. I don't have the visibility

Re: [DISCUSS] Revisiting Java 11's experimental status

Zgc > On Jul 14, 2020, at 2:26 AM, Robert Stupp wrote: > >  >> On 14. Jul 2020, at 07:33, Jeff Jirsa wrote: >> >> Perhaps the most notable parts of jdk11 (for cassandra) aren’t even prod >> ready in jdk11 , so what’s the motivation and what does the project gain >> from revisiting the

Re: [DISCUSS] Revisiting Java 11's experimental status

If I understand correctly, you’re proposing to “officially support” Java 8 and 11 (i.e. remove the “experimental” tag for Java 11). +1 on that from my side. It totally makes sense to me for 4.0. Don’t want to hijack the original thread (as it’s just about C* 4.0), but some thoughts about

Re: [DISCUSS] Revisiting Java 11's experimental status

> On 14. Jul 2020, at 07:33, Jeff Jirsa wrote: > > Perhaps the most notable parts of jdk11 (for cassandra) aren’t even prod > ready in jdk11 , so what’s the motivation and what does the project gain from > revisiting the experimental designation on jdk11? Can you elaborate on what’s not even

Re: [DISCUSS] Revisiting Java 11's experimental status

> 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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

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

Re: [DISCUSS] Revisiting Java 11's experimental status

> 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