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

Separate KV2 metadata and data keys #67

Closed
fishi0x01 opened this issue Jan 29, 2021 · 0 comments · Fixed by #68
Closed

Separate KV2 metadata and data keys #67

fishi0x01 opened this issue Jan 29, 2021 · 0 comments · Fixed by #68
Assignees
Labels
enhancement New feature or request

Comments

@fishi0x01
Copy link
Owner

metadata and data keys in KV2 are treated equally at the moment.
However, when implementing key/data modification commands such as replace with regexp, this might lead to unexpected and bad behavior.

For that reason, there must be a unified way to separately interact with metadata and data keys in KV2 backends. By default, metadata keys should be ignored by data modification commands.

@fishi0x01 fishi0x01 added the enhancement New feature or request label Jan 29, 2021
@fishi0x01 fishi0x01 self-assigned this Jan 29, 2021
This was referenced Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant