feat(hive): Add 4.2.1, drop 4.0.1 - #1637
Merged
Merged
Conversation
lfrancke
force-pushed
the
feat/hive-421-drop-40x
branch
from
September 14, 2026 11:44
f865607 to
86ab5dc
Compare
Hive 4.0.1 removed get_table and get_table_objects_by_name from the metastore Thrift interface. Any client built against a Hive 2.3 metastore client still calls them, and that is what Spark bundles: 2.3.9 in Spark 3.5, 2.3.10 in Spark 4.0 through 4.2. Iceberg's HiveCatalog reaches the metastore through IMetaStoreClient and therefore uses whichever client Spark supplies, so an Iceberg job against a Hive 4.0.1 or newer metastore fails. This restores the methods as they were in Hive 4.0.0.
Hive 4.2.1 was previously recorded as blocked because upstream had not published hive-iceberg-catalog, hive-iceberg-handler or hive-hcatalog-server-extensions at that version. That is stale: two of the three are on Maven Central at 4.2.1, the third (hcatalog-server-extensions) is absent at 4.2.0 as well, which we have shipped all along, and all three are modules of the Hive reactor. The preceding change makes the build resolve them from the reactor rather than from Maven Central, so what upstream published stopped mattering. 4.2.1 builds clean, with the same restored Thrift methods and the same single externally-sourced jar (hive-storage-api) as 4.2.0. Patches 0001-0004 applied to 4.2.1 without rebasing; 0005 and 0006 were regenerated by the generator, which verifies its thrift toolchain by requiring that the unmodified IDL regenerates Hive's committed sources byte-for-byte. The OPA authorizer image is pinned per Hive version, so it gains a 4.2.1 variant; it is built from source with hive-version as a build argument, so this costs nothing upstream. 4.0.1 is the one version we ship that serves neither the old Thrift methods nor our patch: it is where HIVE-26537 landed, and it is shipped as upstream released it. Anyone on it is already broken against Iceberg, so moving them to 4.2.1 is a fix rather than a cost. 4.0.0 stays for one more release. It predates the removal and serves the methods natively, so it is unaffected by the Iceberg problem, and keeping it means a user running it in 26.7 can upgrade the platform first and Hive afterwards instead of being forced to do both in the same window. It can go once that upgrade path has been available for a release.
lfrancke
force-pushed
the
feat/hive-421-drop-40x
branch
from
September 14, 2026 11:47
86ab5dc to
9d2c38d
Compare
lfrancke
added this pull request to stack #1638
September 14, 2026 12:23
lfrancke
marked this pull request as ready for review
September 14, 2026 12:23
#1638, #1641 and #1664 landed on main and appended to the same Fixed section and link-definition block this branch adds to. Merged rather than rebased so the reviewed commit stays untouched and the PR gains a commit rather than a rewrite. The resolution is mechanical: both sides' entries kept, link definitions sorted.
Picks up the main merge from the parent branch, resolving the same CHANGELOG collision. Merged rather than rebased so the reviewed commit stays untouched.
Member
Author
|
conflict resolution... |
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 22, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 22, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 22, 2026
NickLarsenNZ
moved this from Development: Waiting for Review
to Development: Done
in Stackable Engineering
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #1636
What this does
4.2.14.0.14.0.0for one more release