rangareddy commented on issue #17228: URL: https://github.com/apache/hudi/issues/17228#issuecomment-5366111481
This issue was reviewed as part of the JIRA-migrated backlog triage (HUDI-5117). **Findings: still unsupported - but this ticket is now actionable in this repository, which it was not when filed.** **The connector moved here.** The Trino Hudi connector was migrated into the Hudi repo by commit `c3c936790727`, *"feat(trino): Migrate the Trino-Hudi connector into the Hudi repo (RFC-105)"* (#18837, 2026-07-27). It lives in `hudi-trino/` (`HudiConnector`, `HudiMetadata`, `HudiPageSource`, `HudiSplitManager` and friends) with its own CI in `.github/workflows/hudi_trino_ci.yml`, `hudi_trino_compat.yml` and `hudi_trino_e2e.yml`. That matters for triage: this sub-task and its six siblings under HUDI-5115 were written when the connector lived in `trinodb/trino`, so they read as out of scope for this repo. They are not - the work can now be done here. **Still read-only.** `HudiMetadata` overrides none of the `ConnectorMetadata` write methods, and searching `hudi-trino/src/main/java` for `createSchema`, `dropSchema`, `createTable`, `beginCreateTable`, `beginInsert`, `beginUpdate` or `beginMerge` returns nothing. So `CREATE TABLE AS` (which needs `beginCreateTable`) is unimplemented. The seven siblings are #17155 (CREATE SCHEMA), #17218 (DROP SCHEMA), #17227 (CREATE TABLE), #17228 (CREATE TABLE AS), #17229 (DROP TABLE), #17226 (UPDATE TABLE) and #17210 (MERGE INTO). They share one prerequisite - the connector needs a write path at all (a `ConnectorMetadata` write surface plus a Hudi write client wired into Trino's transaction model) - so doing them individually will not work. Suggest re-scoping HUDI-5115 around that foundation first, now that the code is in-tree. 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]
