You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's because catalogOps was not initialized originally, and the asynchronous thread that eliminated the catalog cache made another initialization to close catalogOps, resulting in the default schema being created again.
The deletion logic of the Kafka catalog is as follows:
The initialization of "close" is performed after line 514.
…og (#3672)
### What changes were proposed in this pull request?
avoid to initialize catalog ops when closing catalog
### Why are the changes needed?
Fix: #3673
### Does this PR introduce _any_ user-facing change?
no
### How was this patch tested?
no
…og (#3672)
### What changes were proposed in this pull request?
avoid to initialize catalog ops when closing catalog
### Why are the changes needed?
Fix: #3673
### Does this PR introduce _any_ user-facing change?
no
### How was this patch tested?
no
…og (#3679)
### What changes were proposed in this pull request?
avoid to initialize catalog ops when closing catalog
### Why are the changes needed?
Fix: #3673
### Does this PR introduce _any_ user-facing change?
no
### How was this patch tested?
no
Co-authored-by: mchades <[email protected]>
diqiu50
pushed a commit
to diqiu50/gravitino
that referenced
this issue
Jun 13, 2024
… catalog (apache#3672)
### What changes were proposed in this pull request?
avoid to initialize catalog ops when closing catalog
### Why are the changes needed?
Fix: apache#3673
### Does this PR introduce _any_ user-facing change?
no
### How was this patch tested?
no
Version
main branch
Describe what's wrong
drop kafka catalog maybe failed after altering
Error message and/or stacktrace
How to reproduce
Additional context
CatalogKafkaIT accidentally triggered
It's because catalogOps was not initialized originally, and the asynchronous thread that eliminated the catalog cache made another initialization to close catalogOps, resulting in the default schema being created again.
The deletion logic of the Kafka catalog is as follows:
https://github.com/datastrato/gravitino/blob/a09420dd90a413a4f4944fc628286d20f9950d1c/core/src/main/java/com/datastrato/gravitino/catalog/CatalogManager.java#L499-L525
The text was updated successfully, but these errors were encountered: