Skip to content
New issue

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

[Feature] [BanyanDB] Support clean/delete unused measure/stream/indexRule after OAP finished db schema install. #12826

Closed
3 tasks done
wankai123 opened this issue Dec 4, 2024 · 1 comment
Assignees
Labels
backend OAP backend related. feature New feature rejected The issue or PR can't be accepted by upstream.
Milestone

Comments

@wankai123
Copy link
Member

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

Now OAP supports updating the BanyanDB schema when starting, but due to installation process constraints, OAP couldn't clean/delete unused measure/stream/indexRule if the schema changed.

We need a mechanism to support cleaning them after the schema installation.

Use case

No response

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

  • Yes I am willing to submit a pull request on my own!

Code of Conduct

@wankai123 wankai123 added the feature New feature label Dec 4, 2024
@wankai123 wankai123 self-assigned this Dec 4, 2024
@wu-sheng
Copy link
Member

I think we don't need this anymore. We have #12442 as a key new solution to move from one group to another.
We should not worry about scheme update anymore.

@wu-sheng wu-sheng added backend OAP backend related. rejected The issue or PR can't be accepted by upstream. labels Jan 24, 2025
@wu-sheng wu-sheng added this to the 10.2.0 milestone Jan 24, 2025
@wu-sheng wu-sheng closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend OAP backend related. feature New feature rejected The issue or PR can't be accepted by upstream.
Projects
None yet
Development

No branches or pull requests

2 participants