Expose Range Query (Beta) #281
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.
A large PR on implementing the range query.
Supported Types:
(I have no idea how RangeQuery over text works though tantivy supports it, feel free to correct me but now I just make it unavailable)
Changes:
Documentadd_ip_addrmethod for feature parity fromfrom_dictwithSchemaBuilder's schemaFieldTypeasTypemight confuse python users with thetyping.TypeclassDocument'sadd_jsonmethodQuery.range_querymethodExpected Usage:
As the RangeQuery involves a lot of types, I would like to have a more comprehensive review before rolling out to main.