Switch to indexed serialization#33512
Merged
antiguru merged 2 commits intoMaterializeInc:mainfrom Sep 4, 2025
Merged
Conversation
8ba57e1 to
d1c3e70
Compare
petrosagg
approved these changes
Sep 4, 2025
Switch column from sequence to indexed serialization. The difference is that sequence stores data as a sequence of (length, data) and indexed puts all lengths first, followed by all data. We expect this to be more efficient if we do not read all data, or repeatedly borrow its serialized representation. For details, see frankmcsherry/columnar#30 Signed-off-by: Moritz Hoffmann <mh@materialize.com>
Signed-off-by: Moritz Hoffmann <mh@materialize.com>
d1c3e70 to
4222ef1
Compare
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.
Switch column from sequence to indexed serialization. The difference is that sequence stores data as a sequence of (length, data) and indexed puts all lengths first, followed by all data. We expect this to be more efficient if we do not read all data, or repeatedly borrow its serialized representation.
For details, see frankmcsherry/columnar#30