I'm still working on this and have created a WIP pull request to
demonstrate the list of changes: https://github.com/apache/arrow/pull/43050
Laurent
On Mon, May 6, 2024 at 9:40 AM Laurent Goujon wrote:
> I wanted to share some status updates: I do have a list of changes to
> build Arrow with a
I wanted to share some status updates: I do have a list of changes to build
Arrow with a recent version of Java using the `--release` plugin option of
javac.
The full change is available at: https://github.com/laurentgo/arrow/pull/3
Here are roughly how the changes are divided:
* Change access to
I can give it a try for sure
On Fri, Apr 5, 2024 at 10:26 AM Dane Pitkin
wrote:
> I think we can revisit the discussion soon for dropping Java 8 altogether,
> since Spark will release 4.0 in ~June supporting Java 17+ at runtime.
>
> I'm curious how big of an effort it would be to get your propos
I think we can revisit the discussion soon for dropping Java 8 altogether,
since Spark will release 4.0 in ~June supporting Java 17+ at runtime.
I'm curious how big of an effort it would be to get your proposal
implemented. Would you be willing to draft a PR so we can see what types of
changes are
Yes, correct for language features. My point was more that we can
decide on a major Arrow version upgrading the target language version.
That's what I meant by "consensus".
Regards
JB
On Tue, Apr 2, 2024 at 5:55 PM Laurent Goujon
wrote:
>
> At code level we need to separate language features fro
At code level we need to separate language features from library features?
It should be possible to leverage memory API for example through reflection
and/or multi-release jar files, but record is a language feature and it
would not possible to use it without targeting java 17 at the source level.
Hi Laurent
It makes sense to me. I started this "move" (on the plugin side of the
thing) as part of the reproducible build effort.
At code level, I think it would be great to leverage some features
from Java 17+ (I'm thinking about record, memory API, etc).
I would be more than happy to help on t
Hello Arrow Java developers,
I would wonder if the community would be okay to change the minimum Java
version used by the build toolchain to at least Java 17 or 21 (or even 22).
This is different from changing the minimum Java version used at runtime
which would still be 8 (following the vote from
