Re: Updating to Java 11

That makes sense, Gabor. I was under the impression that most projects were already on 17, but this turned out not to be the case. Good to double-check, thanks! Aaron, I think that's a separate discussion, but as mentioned on the Release Cadence, it would make sense for the October release. This m

Re: Updating to Java 11

Would this be part of a 2.0.0 release? On Tue, Sep 16, 2025 at 7:40 AM Gábor Szádovszky wrote: > Hey Fokko, > > I completely agree with dropping Java 8. > We are currently on Java11 for runtime at Dremio. Your list (thanks for > that) also suggests that Java11 would be a safer first step. > > Ch

Re: Updating to Java 11

Hey Gábor, Thanks for chiming in here. Are there any projects in particular that you're concerned about? Moving first to JDK11 also works for me, but I really think we should drop Java 8 since we've released 1.16.0. Some related/dependent libraries: - Spark 4.x is JDK17/21 - Hive 4.0 is JD

Re: Updating to Java 11

Hey Fokko, I completely agree with dropping Java 8. We are currently on Java11 for runtime at Dremio. Your list (thanks for that) also suggests that Java11 would be a safer first step. Cheers, Gabor Fokko Driesprong ezt írta (időpont: 2025. szept. 16., K, 14:20): > Hey Gábor, > > Thanks for c

Re: Updating to Java 11

parquet-java is quite low in the dependency stack of many systems. Do we have info about other OSS projects depending on parquet-java? I feel that upgrading to target JRE11+ would be enough for one step. Gabor Cheng Pan ezt írta (időpont: 2025. szept. 16., K, 5:22): > +1 for moving to JDK17+ >

Re: Updating to Java 11

>From the perspective of maintenance overhead, I think moving to JDK17+ is a good idea. On Tue, Sep 16, 2025 at 2:07 AM Aaron Niskode-Dossett wrote: > > I'm not a PMC member or committer, but I support this. > > On Tue, Sep 2, 2025 at 4:20 PM Fokko Driesprong wrote: > > > Hey everyone, > > > > S

Re: Updating to Java 11

+1 for moving to JDK17+ Thanks, Cheng Pan > On Sep 16, 2025, at 11:15, Gang Wu wrote: > > From the perspective of maintenance overhead, I think moving to JDK17+ > is a good idea. > > On Tue, Sep 16, 2025 at 2:07 AM Aaron Niskode-Dossett > wrote: >> >> I'm not a PMC member or committer, but

Re: Updating to Java 11

I'm not a PMC member or committer, but I support this. On Tue, Sep 2, 2025 at 4:20 PM Fokko Driesprong wrote: > Hey everyone, > > Since Parquet 1.16.0 has been released, I wanted to resurface this thread > in your mailbox. How do we feel about moving to JDK17+? > > Kind regards, > Fokko > > Op v

Re: Updating to Java 11

Hey everyone, Since Parquet 1.16.0 has been released, I wanted to resurface this thread in your mailbox. How do we feel about moving to JDK17+? Kind regards, Fokko Op vr 21 mrt 2025 om 11:55 schreef Steve Loughran : > FWIW hadoop is looking at 3.5.0 being java 17+ only, with a goal of getting >

Re: Updating to Java 11

We agreed on a release cadence a while ago with quarterly releases. This is pretty much buried under the how-to-release guide. Maybe we should make this a separate page, and I like the idea of also communicating th

Re: Updating to Java 11

> > > - Release 2.0.0 with planned tasks including Java 11 support and deprecated > API cleanup. > I'm glad you mentioned the deprecated API cleanup. The modules I'm most familiar with (parquet-thrift and parquet-protobuf) have many, many methods marked for removal in 2.0.0. I would be happy to

Re: Updating to Java 11

FWIW hadoop is looking at 3.5.0 being java 17+ only, with a goal of getting out this year. Java8 has been nice and stable but it's time is over. retiring it will reduce the test configurations while letting us use all the new features added in the last 5+ years. java23 work is ongoing too...mainl

Re: Updating to Java 11

I agree that dropping Java 8 should happen after we have released new features like geometry and variant types. It would be good to set the expectation of future releases (even without precise date) so they can be planned. For example: - Release 1.16.0 for geometry and variant initial implementati

Re: Updating to Java 11

Hey Eugene, Gang, Thanks for bringing this up. Should we create an issue targeting milestone 2.0 ? We've taken the first steps to drop Java 8, like Hadoop 2.x. I think with the new types like Variant and Geo coming up, I think it is reasonable

Re: Updating to Java 11

Thanks for bringing this up! I think this requires a major version bump which has been discussed at [1]. According to our release cadence [2], should we plan a parquet-java 2.0.0 release with action items like dropping Java 8 support? [1] https://lists.apache.org/thread/kttwbl5l7opz6nwb5bck2gghc2

Updating to Java 11

Our team is looking for a resolution on https://github.com/apache/parquet-java/pull/1308 The issue with the build appears to be that parquet-java is build on Java 8 while the new protobuf library is built on Java 11. `wgtmac` mentioned that I should reach out to this dev group for a wider audie