Actually, I think as long as hadoopClient supports JDK 25+, we can just reuse the compatibility layer we built for the older Hadoop versions—it should work just as well.
---- Replied Message ---- | From | Ayush Saxena<[email protected]> | | Date | 01/19/2026 17:19 | | To | dev<[email protected]> | | Cc | | | Subject | [DISCUSS] Thoughts on JDK 25 (LTS) adoption for Hive | Hi folks, As we know, JDK 25 has been released and is now the latest LTS. I wanted to start a discussion on whether and when it makes sense for Hive to start chasing it. From what I’ve read so far, the release looks solid and there are generally positive signals around it, which makes it an interesting option to consider. I also had a few offline discussions last week, and a common sentiment was that it might be a bit early to move aggressively. Our last major shift was to JDK 21, and much of the Hadoop ecosystem isn’t moving at the same pace. Given that, an immediate jump may be ambitious. One possible middle ground could be to acknowledge JDK 25 as a target, but not aim for it in the very next release—perhaps instead in the one after that, once the ecosystem has had more time to catch up. I haven’t done any hands-on validation yet, so I can’t comment concretely on what might break or the level of effort involved. That said, from some initial looking around, a potential prerequisite could be moving to Hadoop 3.5.0+ (or beyond), which in itself could be a blocker. On top of that, there’s the usual question of how third-party dependencies—and our own code—would behave. Would be good to hear what others think: whether this is something we should start planning for now, or keep on the radar and revisit after some more ecosystem movement. -Ayush
