[client] Add support of column value compression - #4183
Draft
zuston wants to merge 1 commit into
Draft
Conversation
zuston
marked this pull request as draft
September 1, 2026 10:06
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
1 participant
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.
Purpose
Primary-key tables can contain large
BYTEScolumns that are transferred and stored without compression, increasing network bandwidth, storage usage, and write costs, especially for the multi-model columns.This change adds per-column
LZ4orZSTDcompression on the client side. Each compressed value uses a self-contained envelope containing a magic number, version, codec, original length, and payload. Readers detect and decode it transparently by default, while legacy uncompressed values remain compatible.Brief change log
Tests
API and Format
Documentation