Skip to content

minor: Upgrade to Hadoop 3.5#19273

Open
jtuglu1 wants to merge 1 commit intoapache:masterfrom
jtuglu1:upgrade-hadoop-version
Open

minor: Upgrade to Hadoop 3.5#19273
jtuglu1 wants to merge 1 commit intoapache:masterfrom
jtuglu1:upgrade-hadoop-version

Conversation

@jtuglu1
Copy link
Copy Markdown
Contributor

@jtuglu1 jtuglu1 commented Apr 7, 2026

Description

https://hadoop.apache.org/release/3.5.0.html

Release note

Upgrade to Hadoop 3.5


This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@jtuglu1 jtuglu1 requested a review from clintropolis April 7, 2026 22:16
@jtuglu1 jtuglu1 force-pushed the upgrade-hadoop-version branch 2 times, most recently from 4535f68 to 8951da0 Compare April 8, 2026 04:17
@github-actions github-actions bot added the GHA label Apr 8, 2026
@jtuglu1 jtuglu1 force-pushed the upgrade-hadoop-version branch from 8951da0 to 202ef1e Compare April 8, 2026 04:18
pom.xml Outdated

<properties>
<java.version>17</java.version>
<java.version>21</java.version>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this PR dropping support for Java 17? Why? I don't have anything against it in principle, but there should be a reason.

Copy link
Copy Markdown
Contributor Author

@jtuglu1 jtuglu1 Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this was the plan all-along (wait for Hadoop 3.5 upgrade then bump to whatever latest JDK version this supports). Since Hadoop 3.5 supports JDK 21 client-side and it is the only thing preventing us from upgrading the compiler version, it seemed correct to do. Whether we wait for JDK 25+ support in Hadoop before decoupling it from critical extensions (e.g. Parquet) is IMO a separate issue, and we can in the meantime upgrade the compiler version as the timeline for the other changes is undefined at the moment. Let me know if you have any hesitations.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll separate these JDK changes into separate change.

@jtuglu1 jtuglu1 force-pushed the upgrade-hadoop-version branch from 202ef1e to 58ab434 Compare April 8, 2026 17:15
@jtuglu1 jtuglu1 requested a review from gianm April 8, 2026 17:21
@jtuglu1 jtuglu1 force-pushed the upgrade-hadoop-version branch 7 times, most recently from c0e17e7 to c7d4dbb Compare April 9, 2026 05:35
@jtuglu1 jtuglu1 force-pushed the upgrade-hadoop-version branch 6 times, most recently from 095af05 to 29efdf2 Compare April 9, 2026 19:35
@jtuglu1 jtuglu1 force-pushed the upgrade-hadoop-version branch from 29efdf2 to 6ee1c59 Compare April 9, 2026 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants