GitHub user voonhous added a comment to the discussion: Native SQL DDL support for Hudi table creation across engines (Trino, Presto etc.)
Point 1 concerns me a bit. Spark SQL already registers through Spark’s catalog/Hive APIs, while the DataFrame Hive-sync path uses `HiveSyncTool`. We already have separate metadata-building paths to keep consistent; introducing another in Trino would increase that maintenance burden. Using Trino’s `HiveMetastore` API makes sense given the dependency constraints, but can we first identify and extract the shared schema/property/storage-descriptor construction into an engine-neutral layer? Each integration could then translate that representation into its own API types, with tests verifying equivalent metastore semantics. I’d prefer a focused refactor here over another independently maintained implementation. GitHub link: https://github.com/apache/hudi/discussions/19484#discussioncomment-18316365 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
