rangareddy commented on issue #16892: URL: https://github.com/apache/hudi/issues/16892#issuecomment-5391423865
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9110). **Findings: partially delivered, and the two engines are in very different places.** **Trino - substantially built.** **Where this lives now.** The Trino Hudi connector was migrated into this repository by commit `c3c936790727` (RFC-105, #18837, 2026-07-27) and is the `hudi-trino/` module, with its own CI workflows. This ticket predates that move, so it reads as out of scope for `apache/hudi` - it is not. The connector already has an index-support framework to extend: `hudi-trino/src/main/java/io/trino/plugin/hudi/query/index/` contains `HudiBaseIndexSupport`, `HudiIndexSupport`, `IndexSupportFactory`, and concrete supports for column stats, partition stats, record-level index and secondary index (plus a `HudiNoOpIndexSupport` fallback). There is **no** expression-index support among them. So data skipping via column stats, partition stats, record-level index and secondary index all exist for Trino today. Expression index is the remaining gap, tracked separately as #16963. **Presto - not started, and not startable here.** There is no `hudi-presto` module in this repository; the only Presto artefacts are docker demo files, `dependencies/hudi-presto-bundle.txt` and `rfc/rfc-44/presto-connector.png`. The connector lives in `prestodb/presto`. The four Presto tickets in this batch (#16957, #16958, #16960, #16969) share that problem. So this umbrella cannot be completed as scoped: the Presto half needs either a decision to bring the connector in-repo (as was done for Trino) or a re-scope of this ticket to Trino only. Keeping this open. -- 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]
