Thanks all for the input. It sounds like it is NOT feasible to maintain a
legacy branch. So when Arrow drops Java 8 (and 11?) support, we should
consider it EOL from Arrow's perspective.
+1 to Fokko's suggestion on waiting. I propose we commit to dropping Java 8
and 11 from Arrow in tandem with
Hey everyone,
Great to bring this up. I can speak for the Iceberg community, and we
expect to support Java 8 for a long time there (unfortunately). Let me go
over some of the arguments here.
Java 8 does have a long Extended Support timeline, but a recent
> report shows Java 11 increasing in
> I cannot estimate the effort to backport large features like the new
layouts that are currently being added (e.g. RunEndEncoding, ListView,
etc.).
In my mind we are only talking about patch releases for security fixes or
similarly critical issues as otherwise the effort to maintain 'v14' (but
I agree that we have to move on. It seems that patch release to
Arrow v14 is a good idea, though I cannot estimate the effort to
backport large features like the new layouts that are currently
being added (e.g. RunEndEncoding, ListView, etc.).
As an Arrow developer, I am always happy to drop JDK
To summarize the discussion so far:
* Some Arrow Java users are still on JDK 8
* Arrow v14 is proposed as the final version with JDK 8 support
* Arrow v14 can support patch releases if necessary for JDK 8 users
* There is an open question to decide if JDK 11 should be dropped
simultaneously
Gang
>From a release engineer perspective (without java knowledge) I agree with
Micah, I'd rather make a patch release for an older version if needed but
modernize the codebase and simplify CI!
On Sat, Oct 7, 2023 at 5:27 AM Micah Kornfield
wrote:
> I think given the stability of Arrow Java,
I think given the stability of Arrow Java, dropping support probably makes
sense. If a bug comes up or consumers really need to new features we can
always make a patch release of an older version.
On Thu, Oct 5, 2023 at 3:13 PM Dane Pitkin
wrote:
> I also learned today that Apache Spark has
I also learned today that Apache Spark has dropped support for Java 8 and
11 for their next release (v4.0)[1]. Should we consider dropping Java 11 as
well?
[1]https://github.com/apache/spark/pull/43005
-Dane
On Thu, Oct 5, 2023 at 3:30 PM Dane Pitkin wrote:
> I created a GH issue[1] proposing
I created a GH issue[1] proposing the removal of Java 8 support. It
would target the Arrow v15 release (~Jan 2024).
IMO it would be in the best interest of the project for two major reasons:
1. Unblock the Java Platform Module System (JPMS)[2] implementation.
2. Unblock Arrow from upgrading
>
> - As a low level library, users have to add specific flags to use
> Java 9 and up with Arrow to resolve issues with java.nio. This has
> been annoying for our customers constantly. If this is not resolved,
> I would say we may see a lot of complaints in the future.
>
I filed issue 37739[1]
Thanks for bringing this up!
I have two concerns of dropping Java 8 support:
- As a low level library, users have to add specific flags [1] to use
Java 9 and up with Arrow to resolve issues with java.nio. This has
been annoying for our customers constantly. If this is not resolved,
I would say
Hi Arrow Java developers,
I would like to propose a timeline for dropping support for Java 8:
- Propose to drop JDK8 in Arrow v15 (2 releases from now)
- JDK 21 support will be added before removal of JDK8
Why?
- Java 8 no longer receives Premier Support (1)
- Some Arrow Java (test) dependencies
12 matches
Mail list logo
