We are using AWS Corretto Java 17 with NiFi 1.20 for 6 months at least. No
issues so far.
On May 31, 2023 6:03:51 p.m. Mike Thomsen wrote:
I'm all in favor of making 17 the requirement for 2.0
On a related note, I was asked by one of our devops guys if 17 was a good
idea for 1.X. I know we
I'm all in favor of making 17 the requirement for 2.0
On a related note, I was asked by one of our devops guys if 17 was a good
idea for 1.X. I know we support it, but is it considered just as good as 11
for 1.21+?
On Wed, May 31, 2023 at 6:15 PM Kevin Doran wrote:
> Yeah I agree it makes
Yeah I agree it makes sense to move to 17… as long as we are introducing a
potential disruptive migration, we should move to the version we can support
longer rather than 11 which will land us back in the same situation we were in
with 8 EOL
From: Pierre Villard
Hey Joe,
I'd recommend doing the move right now and say that NiFi 2.0 requires Java
17. And we would focus on Java 21 with NiFi 3.0.
I honestly don't see any value in absolutely keeping support for Java 11
right now.
Pierre
Le mer. 31 mai 2023 à 19:22, Joe Witt a écrit :
> Team,
>
> We've
Team,
We've discussed in the past having NiFi 2.0 move from Java 8 to Java 11 as
the required minimum while also working on Java 17.
As we move on in time though we are now 4 months (Sept) from. Java 11
openJDK going end of support. Meanwhile, the Spring 5.x line goes end of
support as of next
