helong001 commented on issue #7395: URL: https://github.com/apache/gravitino/issues/7395#issuecomment-2975669824
> > May be we could add a configuration to specifying the default catalog for `dynamic-config-provider`, WDYT? > > I actually mixed both **static** and **dynamic** catalog providers in the same metalake, and that’s when the issue with the default catalog came up — I encountered the error: > > "default_catalog is illegal in gravitino-based-provider" > > After I **commented the static configuration**, everything started to work properly again. That suggests the static provider was still being used to resolve the default catalog. > > How to properly handle this really depends on **whether mixing static and dynamic providers is officially supported**. One possibility is to treat the static configuration as a fallback or default definition layer on top of the dynamic setup. > > If mixing is not intended, then maybe the system should enforce a clear separation — or, alternatively, allow setting a default catalog even in a dynamic-only setup. @FANNG1 Actually, I think there was a misunderstanding. The issue still exists — I didn’t solve it by switching to dynamic config. What actually happened was: I changed the **Iceberg REST catalog backend from rest to jdbc**, and that’s when the behavior changed. The error "default_catalog is illegal in gravitino-based-provider" is still being thrown — it’s coming from **iceberg-rest-25**, not from Gravitino itself. We still need to clarify how the Iceberg REST catalog, when using the Gravitino-based **dynamic config provider**, is supposed to handle default_catalog. -- 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]
