feat(inverted_index.search): add fst applier #2851
Merged
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.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
FstApplier
is a broad term that denotes an abstraction that accepts anFst
and returns values(Vec<u64>
).The primary reason for proposing this abstraction is to allow for preprocessing of certain
Predicate
s, especially forInList
s, so it is known from the outset which keys to retrieve. By using these keys to perform aFst::get()
, the desired results can be obtained. Other predicates have a wider scope and require additional APIs from theFst
, such asfst::range()
andfst::search()
.The
FstApplier
serves as a suitable abstraction to encompass the implementations of the various scenarios described above.Checklist
Refer to a related PR or issue link (optional)
#2705
The next PRs to be submitted:
feat(inverted_index.search): add fst values mapper
feat(inverted_index.search): add index applier