diqiu50 commented on PR #10738: URL: https://github.com/apache/gravitino/pull/10738#issuecomment-4260948281
The root cause is that `dropCatalog(force=false)` checks whether any schemas exist in the entity store, but imported schemas (synced from external catalogs via search listener load) are also written to the entity store — so they were mistakenly treated as user-created schemas, causing a false `NonEmptyCatalogException`. The fix distinguishes user-created schemas from imported ones: a schema is considered user-created only if it carries a `StringIdentifier` in its properties (written by Gravitino when the user creates it via API) or is marked with `gravitino.created=true` in the entity store. However, as @yuqi1129 pointed out, the entity store does not persist properties, so the marker approach needs to be rethought. -- 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]
