rangareddy commented on issue #17021: URL: https://github.com/apache/hudi/issues/17021#issuecomment-5391446628
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9430). **Findings: still open, 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. The blindspot named in the description is worth keeping explicit: test tables are generated with Spark + Hudi, while Flink supports timestamp precisions that `HudiAvroSerializer` does not handle - so a table written by Flink is exactly the case with no coverage. Related in the same area: #17041 (HUDI-9496) reports decimal and timestamp partition values being wrong on the filesystem path, which matters for Trino specifically because it derives partition values from the path rather than the data file. A Flink-written smoke test would likely surface that too, so the two are worth doing together. 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]
