Lookup functions have fields parameter to speed up decoding#7
Merged
Conversation
marselester
force-pushed
the
lookup-fields
branch
from
February 22, 2026 20:09
14baa8e to
895bc76
Compare
marselester
force-pushed
the
lookup-fields
branch
from
February 22, 2026 20:26
895bc76 to
a09e4db
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.
The
fieldsparameter controls which fields to decode (the remaining ones will be empty). If we limit decoding tocityfield, we can get ~83% faster lookups on 1M sample (tested on M2 Pro):city~808K lookups/sec median