Repository navigation
Add support for multiple index columns - #3270
Merged
Merged
Conversation
texodus
force-pushed
the
multi-index-table
branch
from
November 3, 2026 17:32
009bf89 to
28bdf8b
Compare
Signed-off-by: Andrew Stein <steinlink@gmail.com>
texodus
force-pushed
the
multi-index-table
branch
from
November 3, 2026 18:50
28bdf8b to
fa6df5b
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.
This PR adds support for multiple
indexcolumns toTable:Internally, this feature uses a non-utf8, order-preserving, type-aware binary encoding packed in a
t_tscalar::string, which itself is memoized in a dictionary. This slightly improves performance by avoiding e.g. datetime stringification, but the real impact is API support - for streams that need multiple index support, you no longer need to decode + stringify + concat + encode these columns to inject them into Perspective, ideally avoiding encode/decode entirely if the source emitter support Arrow.Multi-index support is backwards compatible, string arguments to
indexstill work and are identical to an array with a single string.