FANNG1 commented on PR #4680: URL: https://github.com/apache/gravitino/pull/4680#issuecomment-2309790657
> In my case, I can reuse the JDBC catalog configurations for my custom catalog, but this approach doesn't cover other custom catalogs. > > Now, we need to enumerate all configuration keys in IcebergCatalogPropertiesMetadata. > > Should we accept all configurations, only those with certain prefixes, or wait until we encounter other cases? > > @FANNG1 WDYT? I prefer to delay supporting the `custom` catalog backend for the Gravitino Iceberg catalog until there are real requirements. -- 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]
