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.

Sign up for GitHub

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

Jump to bottom

Do not use base58 strings as keys in the metabase #1482

Closed
Tracked by #1398
fyrchik opened this issue Jun 6, 2022 · 0 comments · Fixed by #1529
Closed
Tracked by #1398

Do not use base58 strings as keys in the metabase #1482

fyrchik opened this issue Jun 6, 2022 · 0 comments · Fixed by #1529
Assignees
@fyrchik
Labels
neofs-storage Storage node application issues performance More of something per second

Comments

@fyrchik
Copy link
Contributor

fyrchik commented Jun 6, 2022 •
edited
Loading

Depends on #1483.
@fyrchik fyrchik mentioned this issue Jun 6, 2022
Open
11 tasks
@fyrchik fyrchik mentioned this issue Jun 16, 2022
Merged
@carpawell carpawell modified the milestones: v0.31.0, v0.32.0 Aug 4, 2022
@carpawell carpawell removed the blocked Can't be done because of something label Sep 15, 2022
aprasolova pushed a commit to aprasolova/neofs-node that referenced this issue Oct 19, 2022
@fyrchik @aprasolova
[nspcc-dev#1482] metabase: Encode database keys in binary
9a5b61e 
Signed-off-by: Evgenii Stratonikov <evgeniy@morphbits.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fyrchik fyrchik

Labels
neofs-storage Storage node application issues performance More of something per second
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not use base58 encoded keys in the metabase fyrchik/neofs-node
2 participants
@fyrchik @carpawell