deepakpanda93 commented on issue #15481: URL: https://github.com/apache/hudi/issues/15481#issuecomment-5295131506
This issue was reviewed as part of the JIRA-migrated backlog triage. Findings: the blocker reported here no longer applies, on two independent counts. **1. Presto and Trino now start on arm64.** The 2022 failure was the hard architecture check — `Presto requires amd64 or ppc64le on Linux (found aarch64)`. [`hudi-notebooks/`](https://github.com/apache/hudi/tree/master/hudi-notebooks) builds Trino 481 and Presto 0.297 from the official upstream images, both of which publish `linux/arm64`. Verified on an arm64 host: both reached `SERVER STARTED` with `/v1/info` returning 200, and Presto now only warns *"Support for the ARM architecture is experimental"* instead of refusing to start. Worked examples: [`06_hudi_trino_example.ipynb`](https://github.com/apache/hudi/blob/master/hudi-notebooks/notebooks/common/06_hudi_trino_example.ipynb) and [`07_hudi_presto_example.ipynb`](https://github.com/apache/hudi/blob/master/hudi-notebooks/notebooks/common/07_hudi_presto_example.ipynb). **2. The original harness no longer ships these components.** The `presto-coordinator-1`, `presto-worker-1`, `trino-coordinator-1` and `trino-worker-1` services were removed from every file under `docker/compose/` on 2026-07-08 (commit `3015eb944083`, #19203), so the configuration this issue describes cannot be reproduced in the legacy demo. @jonvex — thanks for confirming above; agreed this predates both changes. One caveat worth recording: the hangs and query timeouts reported in 2022 were a **separate** symptom from the architecture check, and have not been re-tested under load on arm64. If those recur on the notebooks stack, please open a fresh issue with the query and a thread dump rather than reopening this one. Closing as resolved. -- 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]
