rangareddy commented on issue #17037: URL: https://github.com/apache/hudi/issues/17037#issuecomment-5391449903
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9480). **Findings: not implemented, and now actionable here.** **Where this lives now.** The Trino Hudi connector was migrated into this repository by commit `c3c936790727`, *"feat(trino): Migrate the Trino-Hudi connector into the Hudi repo (RFC-105)"* (#18837, 2026-07-27). It is the `hudi-trino/` module, with its own CI in `.github/workflows/hudi_trino_ci.yml`, `hudi_trino_compat.yml` and `hudi_trino_e2e.yml`. This ticket was filed when the connector lived in `trinodb/trino`, so it reads as out of scope here - it is not, and can now be worked in this repo. Verified: there is no reference to `ExpressionIndex` or `expression_index` anywhere under `hudi-trino/src/main/java`, so the connector cannot use an expression index for file skipping. The pattern to follow already exists in the module: `hudi-trino/src/main/java/io/trino/plugin/hudi/query/index/HudiColumnStatsIndexSupport.java` is the column-stats equivalent, so this is an addition alongside it rather than new infrastructure. One prerequisite worth checking first: expression index **record generation** is still Spark-only on the Hudi side (`EngineIndexerSupport.generateExpressionIndexRecords`, with `UnsupportedEngineIndexerSupport` for other engines). Reading an existing expression index from Trino is a separate concern from writing one, but it is worth confirming the read path is genuinely engine-neutral before assuming this is purely a connector change. 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]
