+1 for moving to JDK17+ Thanks, Cheng Pan
> On Sep 16, 2025, at 11:15, Gang Wu <[email protected]> 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 > <[email protected]> wrote: >> >> I'm not a PMC member or committer, but I support this. >> >> On Tue, Sep 2, 2025 at 4:20 PM Fokko Driesprong <[email protected]> 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 vr 21 mrt 2025 om 11:55 schreef Steve Loughran >>> <[email protected]>: >>> >>>> 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...mainly changes in the security APIs. >>>> >>>> >>>> >>>> On Thu, 20 Mar 2025 at 13:27, Aaron Niskode-Dossett >>>> <[email protected]> wrote: >>>> >>>>>> >>>>>> >>>>>> - 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 work on those once >>>> 1.17.0 >>>>> is wrapped up. >>>>> >>>>> Best, Aaron >>>>> >>>>> -- >>>>> Aaron Niskode-Dossett, Data Engineering -- Etsy >>>>> >>>> >>> >> >> >> -- >> Aaron Niskode-Dossett, Data Engineering -- Etsy
