Skip to content
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.

Do not return an error when dropping a table that exists in ceresmeta but does not exist in ceresdb #132

Open
chunshao90 opened this issue Jan 15, 2023 · 0 comments
Open

Do not return an error when dropping a table that exists in ceresmeta but does not exist in ceresdb #132

chunshao90 opened this issue Jan 15, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@chunshao90
Copy link
Contributor

Description
Do not return an error when dropping a table that exists in ceresmeta but does not exist in ceresdb.

Proposal

  • handle_drop_table_on_shard in meta_event service support if exists.

Additional context
@chunshao90 chunshao90 added the enhancement New feature or request label Jan 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chunshao90