RFC-0066: Native execution support for Hudi MOR tables - #66
Open
jja725 wants to merge 2 commits into
Open
Conversation
jja725
force-pushed
the
rfc-hudi-mor-native
branch
from
August 17, 2026 21:19
8311e72 to
49eeb94
Compare
jja725
force-pushed
the
rfc-hudi-mor-native
branch
from
August 17, 2026 21:32
49eeb94 to
0508137
Compare
jja725
force-pushed
the
rfc-hudi-mor-native
branch
from
August 17, 2026 22:03
0508137 to
31c8089
Compare
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
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.
Summary
This RFC proposes native execution (Prestissimo/Velox) support for snapshot
SELECTqueries on Hudi MERGE_ON_READ tables. The main piece is a native Hudi connector in Velox, built around a C++ HoodieLogFormat reader and record merger, structured like the existing Iceberg connector. It also covers the Presto native protocol, explicit Hudi handle conversion, coordinator-side compatibility validation, and native catalog registration.The revised design treats Java Hudi behavior as the correctness oracle while acknowledging that native semantic parity will be incremental. Each release declares a compatibility matrix for table versions, log formats, merge modes, payloads, key generation, and schema evolution. Unsupported table configurations fail during planning, and unsupported block details discovered on the worker fail the query; there is no JVM fallback from native execution.
Other key points:
Related: