nsivabalan commented on issue #17058: URL: https://github.com/apache/hudi/issues/17058#issuecomment-4800746557
This appears to be addressed in current master via commit [`42263225e6`](https://github.com/apache/hudi/commit/42263225e631abaa23d4da3f96eb237c3e0cabf1) (PR #13785, HUDI-9771, merged Aug 2025), which superseded the originally-linked PR #13424. Per-catalog database/table-name configs are now available: - **Glue**: `hoodie.datasource.glue_sync.database_name` and `hoodie.datasource.glue_sync.table_name` — defined in `GlueCatalogSyncClientConfig.java` and consumed in `AWSGlueCatalogSyncClient`. - **DataHub**: `hoodie.meta.sync.datahub.database.name` and `hoodie.meta.sync.datahub.table.name` — defined in `DataHubSyncConfig.java` and consumed in `HoodieDataHubDatasetIdentifier`. - **HMS**: Already uses the HMS-specific `hoodie.datasource.hive_sync.database` / `hoodie.datasource.hive_sync.table` keys via `HiveSyncTool` / `HoodieHiveSyncClient`. Each config has an infer function so existing behavior (falling back to `META_SYNC_DATABASE_NAME` / `META_SYNC_TABLE_NAME` / `HOODIE_TABLE_NAME_KEY`) is preserved when the per-catalog override isn't set. `HiveSyncTool` was also refactored to read names from `syncClient.getDatabaseName()` / `getTableName()` so each sub-client (Glue, Hive, etc.) resolves its own pair. Could this issue (and HUDI-9528) be closed? If a specific catalog or scenario is still missing per-catalog support, please reopen with details. -- 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]
