yihua opened a new pull request, #18782:
URL: https://github.com/apache/hudi/pull/18782

   ### Change Logs
   
   Add the design document for **RFC-105**: refactor the Trino Hudi connector 
into a thin Trino-side shim plus a Hudi-published `org.apache.hudi:hudi-trino` 
artifact.
   
   ### Companion PRs / Issues
   
   - Tracking issue: https://github.com/apache/hudi/issues/18780
   - RFC number reservation (must merge first): 
https://github.com/apache/hudi/pull/18781
   
   ### Summary of the design
   
   - **Two artifacts.** `io.trino:trino-hudi` (Trino OSS) becomes a thin shim — 
`HudiPlugin` + test harness only. `org.apache.hudi:hudi-trino` (Hudi OSS, new) 
holds all connector logic at `io.trino.plugin.hudi.*`.
   - **Single Hudi artifact** targets the latest Trino release; assumes 
`trino-spi` backward compatibility (RevAPI-enforced) across recent Trino 
releases.
   - **First publication: Hudi 1.3.0.** Hudi increases release cadence going 
forward to support this integration model.
   - **Separate build target on Hudi side.** `hudi-trino-plugin` is excluded 
from the default `mvn install` reactor (gated by `-Phudi-trino`) because Trino 
requires Java 25.
   - **Two new CI workflows on Hudi side**: full test suite run on every PR 
touching `hudi-trino-plugin`, and a nightly compile-against-latest-Trino-master 
check to catch SPI drift before a Trino release ships.
   - **Full test duplication.** Trino-side keeps a comprehensive test suite 
(per @raunaqm's condition); Hudi-side mirrors them and additionally expands 
coverage.
   - **Trino-side shim PR** is small and obviously correct — deletes code and 
points at the published artifact.
   
   ### Motivation (community alignment)
   
   The Trino-side Hudi connector has stalled — four stacked Hudi-side 
improvement PRs (trinodb/trino#28518, #28533, #28644, #28645) were closed by 
Trino's stale-bot for lack of review. In the `#dev` Slack thread, Trino 
maintainer @raunaqm proposed reducing Trino's Hudi connector to a thin shim 
around a Hudi-published library; Hudi community (@yihua, @voonhous) accepted 
with @raunaqm's condition of maintaining a comprehensive test suite on Trino 
side.
   
   Stakeholders aligned: Hudi — @yihua, @voonhous, @bhasudha. Trino — @raunaqm, 
@ebyhr, @mariusgrama, @findepi, @manfred-moser.
   
   ### Impact
   
   Documentation-only — adds `rfc/rfc-105/rfc-105.md`. No code changes in this 
PR. Implementation will follow per the rollout plan in the RFC.
   
   ### Risk level (write none, low medium or high below)
   
   none
   
   ### Documentation Update
   
   Adds `rfc/rfc-105/rfc-105.md` (full RFC document).
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Change Logs and Impact were stated clearly
   - [x] Adequate tests were added if applicable (N/A — design doc)
   - [x] CI passed
   
   cc @codope @bhasudha @vinothchandar @raunaqm


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to