-
Notifications
You must be signed in to change notification settings - Fork 37
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
Build full searchv2-compatible index from chained meta #3139
Comments
@roman-khimov, got some problem: metaservice was done to follow initial requirements to be based on a true KV DB from neo-go's repo (#3070, "forget about buckets, use prefixes for everything"). Does not mean neo-go is the reason, it just was meant to be based on a simple KV. Current metabase implementation uses buckets: neofs-node/pkg/local_object_storage/metabase/metadata.go Lines 75 to 142 in d9c3652
|
SV2 operates on a well-known DB structure. As long as you can make the same structure (even if there is an additional prefix added, this can be handled, but better without it) --- you're OK. Buckets are totally irrelevant here. |
So "structure" is a general term? It does not need to be handled by the same code and implementation may vary, yes? |
The more code you can reuse the better. |
No description provided.
The text was updated successfully, but these errors were encountered: