Repository navigation
chore(deps): bump tantivy from 0.22.1 to 0.27.0 - #51
Merged
Merged
Conversation
Adapt to the 0.27 API: TopDocs needs order_by_score() to be a collector, RangeQuery::new takes Term bounds (new_i64_bounds is gone), and stored values are read through the Value trait instead of matching OwnedValue. Index format goes 6 -> 7; 0.27 still opens format >= 4, so existing indexes load. New segments are format 7, which 0.22 cannot read.
dubadub
force-pushed
the
fix/tantivy-0.27
branch
from
November 10, 2026 10:28
edde30f to
03537ad
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.
Replaces #48, which fails to compile against the 0.27 API.
TopDocsis no longer aCollectoron its own: add.order_by_score().RangeQuery::new_i64_boundsis gone: useRangeQuery::newwithTerm::from_field_i64bounds.Valuetrait (as_str/as_i64) instead of matchingOwnedValue.Index format: 0.27 writes format 7 and still reads format >= 4, so the existing (format 6) index opens. Rolling back to 0.22 after new segments are written would need a reindex.
Verified locally:
cargo build --all-targets,cargo clippy --all-targets --all-features -D warnings,cargo fmt --check,cargo testall pass.