[Feature] Manage properties in BanyanDB

[wu-sheng]

Search before asking

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

Description

At the beginning of BanyanDB, we picked etcd to store metadata and properties by leveraging etcd's existing features. With time, measure and stream models become more stable. Considering keeping the consistent ownership, and increasing the maintenance and Backup and Restore Data, we could host this data by BanyanDB itself.

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

• I agree to follow this project's Code of Conduct

[hanahmily]

We will utilize the inverted index to implement the new 'Property.' It will inherit some features from the time-series data structure, such as 'sharding.' However, the 'Property' does not support any 'TTL' settings.

[wu-sheng]

But we don't have sharding parameters when create property. Do you mean we will have a break for this replacement?

[hanahmily]

But we don't have sharding parameters when create property. Do you mean we will have a break for this replacement?

From the API's perspective, there is no change here because the sharding parameters are on the Group. However, the OAP needs to adjust the parameter to set at least one shard. If we can default the shardNum to 1, the OAP doesn't need any alterations.