We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tech debt reduction
After dropping the database(After the L41), we should invalidate the schema name key cache on the frontend node.
greptimedb/src/common/meta/src/ddl/drop_database/metadata.rs
Lines 32 to 43 in c00c1d9
Here is an example of how we invalidate table cache on the frontend node.
invalidate
greptimedb/src/common/meta/src/ddl/drop_table/executor.rs
Lines 114 to 131 in c00c1d9
greptimedb/src/frontend/src/heartbeat/handler/invalidate_table_cache.rs
Lines 38 to 56 in c00c1d9
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What type of enhancement is this?
Tech debt reduction
What does the enhancement do?
After dropping the database(After the L41), we should invalidate the schema name key cache on the frontend node.
greptimedb/src/common/meta/src/ddl/drop_database/metadata.rs
Lines 32 to 43 in c00c1d9
Here is an example of how we invalidate table cache on the frontend node.
invalidate
on the Metasrv; The metasrv will broadcast cache invalidation notifications to frontend nodes.greptimedb/src/common/meta/src/ddl/drop_table/executor.rs
Lines 114 to 131 in c00c1d9
greptimedb/src/frontend/src/heartbeat/handler/invalidate_table_cache.rs
Lines 38 to 56 in c00c1d9
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: