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] [Breaking Change] Adopt new property storage in BanyanDB 0.8 #12919

Closed
2 of 3 tasks
wu-sheng opened this issue Jan 2, 2025 · 1 comment
Closed
2 of 3 tasks
Assignees
Labels
backend OAP backend related. feature New feature
Milestone

Comments

@wu-sheng
Copy link
Member

wu-sheng commented Jan 2, 2025

Search before asking

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

Description

According to #12664, we are moving property storage back to natively in BanyanDB data node, rather than relying on etcd. So, the query protocol is going to follow regular query requests.

Use case

No response

Related issues

The BanyanDB client Java is going to change as well.

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

@wu-sheng wu-sheng added backend OAP backend related. feature New feature labels Jan 2, 2025
@wu-sheng wu-sheng added this to the 10.2.0 milestone Jan 2, 2025
@wu-sheng
Copy link
Member Author

wu-sheng commented Jan 8, 2025

This is done through #12936

@wu-sheng wu-sheng closed this as completed Jan 8, 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
Projects
None yet
Development

No branches or pull requests

2 participants