rangareddy commented on issue #17042: URL: https://github.com/apache/hudi/issues/17042#issuecomment-5391450577
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-9497). **Findings: needs a reproduction; the body has no detail to work from.** **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 body carries only the JIRA link, so there is no query, table shape, or thread dump. "Hanging" is the hardest symptom to act on without one - it could be split generation, a metadata-table lookup that never completes, or a page-source read. What I can confirm is that the component exists and is the plausible locus: `hudi-trino/src/main/java/io/trino/plugin/hudi/query/index/HudiColumnStatsIndexSupport.java`, with column stats gated through `HudiConfig` and `HudiSessionProperties` - so the failing configuration can at least be described precisely. To make this actionable, three things would be enough: the query, whether it hangs during split generation or during reads, and a `jstack` from a hung worker. 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]
