GitHub user voonhous added a comment to the discussion: Native SQL DDL support for Hudi table creation across engines (Trino, Presto etc.)
Following up on the scoping question above, on process and ownership. **On who drives it** Being straightforward about how this works, since you asked whether to formalize it: the [RFC process](https://hudi.apache.org/contribute/rfc-process) expects a champion who carries the proposal through design and implementation. Our RFC table has an `ABANDONED` status for a reason -- proposals without someone driving them stall regardless of merit. Committer attention here is finite and tends to follow whatever has an owner, so the honest answer to "should this be an RFC" is that it's worth one exactly when someone intends to build it. If that's you or your team, I'd genuinely encourage starting at stage 0. It's well-scoped, it's a real improvement on its own, and it's a reasonable first contribution to the module. I can commit to design review, PR review, and helping you navigate the module specifics -- the build is profile-gated and JDK 25 (`mvn -Phudi-trino -pl hudi-trino compile`, tests behind the additional `hudi-trino-tests` profile), which is the sort of thing that costs a newcomer a day otherwise. One scoping note: I'd keep this Trino-only. Presto's Hudi connector lives in `prestodb/presto` and shares none of this code, so folding it in would make the proposal unactionable. GitHub link: https://github.com/apache/hudi/discussions/19484#discussioncomment-17904464 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
