Document native Roaring bitmaps - #3715
Draft
aviggiano wants to merge 2 commits into
Draft
Conversation
Collaborator
|
Hi @aviggiano. Thank you for this PR. Which Redis Open Source release will contain this new feature? I know it's not in 8.10, because it's just about closed. Is it for 8.12? Your PR target needs to be a release-specific feature branch, not main. Once you answer the above, I will create the appropriate branch and then you can edit your PR. Also, this repo does not allow slashes ( |
Author
|
Thanks, it's still unclear which release this will be targeted I'll sync with @sundb and will update the PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BITOPbehaviorbitmapreturn value to theTYPEcommand referenceWhy
The native Roaring bitmap feature in redis/redis#15331 adds an opt-in representation with an important compatibility boundary: bitmap commands work transparently, while generic string commands do not operate on native bitmap values. Users need that behavior and the rollout requirements documented before enabling the feature.
User impact
Users can evaluate whether Roaring compression fits their workload, enable it safely, understand when existing strings convert, and upgrade replicas and persistence consumers before rollout.
Validation
git diff --check