; >> > > our
> > >> > > > > heap usage which is valuable in cloud/shared compute contexts.
> > >> > > > >
> > >> > > > > Performance benefits of Java 21?
> > >> > > > > It appears from some analysis found with googling that Java 21
> > >>
; >> > > out
> >> > > > > of the box 4-5% performance increases generally. Not amazing
> but
> >> > > useful.
> >> > > > >
> >> > > > > User experience otherwise with Java 21?
> >> > > > > I believe it woul
>> > > > > new minimum bar that lives for as long as the 2.x release line
>> lives
>> > > I'd
>> > > > > like to set it at the current LTS available when we ship that
>> line as
>> > > > well.
>> > > > >
&
> I'd
> > > > > like to set it at the current LTS available when we ship that line
> as
> > > > well.
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > >
> > > >
requiring java 21. Starting off as "up to date" as possibly
> > > makes a
> > > > > lot of sense, and some of the new features seem especially relevant
> > to
> > > > NiFi.
> > > > >
> > > > > I definitely understand
es a
> > > > lot of sense, and some of the new features seem especially relevant
> to
> > > NiFi.
> > > >
> > > > I definitely understand the concerns about organizations being
> willing
> > /
> > > > able to approve Java 21...
to support java 17 &
> NiFi
> > > 1.x for some time, so hopefully those groups will have the time they
> need
> > > to get approvals, do evaluations, and upgrade.
> > >
> > > Brandon
> > >
> > > From: Pier
ut those same organizations might also be
> > hesitant to move to NiFi 2.0. We will continue to support java 17 & NiFi
> > 1.x for some time, so hopefully those groups will have the time they need
> > to get approvals, do evaluations, and upgrade.
> >
> > Brandon
> &
> From: Pierre Villard
> Sent: Thursday, September 7, 2023 6:15:58 AM
> To: dev@nifi.apache.org
> Subject: Re: [discuss] nifi 2.0 and Java 21…
>
> Hi all,
>
> I share the concerns raised by Chris regarding how quickly users of NiFi
> will be able to adopt J
r 7, 2023 6:15:58 AM
To: dev@nifi.apache.org
Subject: Re: [discuss] nifi 2.0 and Java 21…
Hi all,
I share the concerns raised by Chris regarding how quickly users of NiFi
will be able to adopt Java 21.
While I'm definitely in favor of using the latest and greatest, especially
when it bring
Hi all,
I share the concerns raised by Chris regarding how quickly users of NiFi
will be able to adopt Java 21.
While I'm definitely in favor of using the latest and greatest, especially
when it brings to the table such significant features, we need to be
careful as it may significantly delay
Yeah, I understand the need to move to 21 as a minimum to take advantage of
its features. Hopefully the wider java ecosystem won't be an issue in the
short term.
I just wanted the discussion to be clear about this being a change to the
Java baseline/minimum for NiFi 2.0.
It's a +1 from me.
On
Chris
My suggestion is rooted in making Java 21 the minimum of the NiFi 2.0
line. It would not work on Java 17. The reason for this is so that we can
leverage the longest duration of a given LTS line while also benefiting
from the language improvements that affords. Maintaining compatibility
To be clear, is the discussion one of making Java 21 the minimum
requirement for NiFi 2.0.0, or rather NiFi 2.x be compatible with Java 21,
while retaining Java 17 as a minimum?
If we moved straight to a Java 21 requirement, will we run into
compatibility issues that delay initial NiFi 2 release?
+1 100%
On Wed, Sep 6, 2023 at 11:48 AM Adam Taft wrote:
> Yes, please. +1 Exactly what Mark said. Virtual threads have potential to
> be extremely impactful to applications like NiFi.
>
> /Adam
>
> On Wed, Sep 6, 2023 at 7:26 AM Mark Payne wrote:
>
> > Thanks for bringing his up, Joe.
> >
> >
Yes, please. +1 Exactly what Mark said. Virtual threads have potential to
be extremely impactful to applications like NiFi.
/Adam
On Wed, Sep 6, 2023 at 7:26 AM Mark Payne wrote:
> Thanks for bringing his up, Joe.
>
> I would definitely be a +1. I think the new virtual thread concept would
>
Thanks for bringing his up, Joe.
I would definitely be a +1. I think the new virtual thread concept would have
great impact on us.
It would allow us to significantly simplify our scheduling logic, which would
help with code maintainability
but would also make configuration simpler. This is one
Team
Thought it might be worth relighting this thread with Java 21 GA imminent.
Given the timing we should give consideration to having Java 21 as the
basis for nifi 2.x to buy maximum time with LTS alignment. There are also
a couple interesting language features we can likely take advantage of.
18 matches
Mail list logo
