Fix stale JSON range query note and ARCHITECTURE.md link

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
ZainnQureshii
2026-10-14 21:47:29 +02:00
committed by PSeitz
co-authored by Claude Opus 5.5
parent 7fea2ab8d8
commit 8a4cfc40f5
2 changed files with 4 additions and 3 deletions
+1 -1
View File
@@ -84,7 +84,7 @@ Indeed, while having several segments instead of one does not hurt search too mu
The user of the library usually does not need to know about the existence of Segments.
Searching is done through an object called a [`Searcher`](src/core/searcher.rs), that captures a
snapshot of the index at one point of time, by holding a list of [SegmentReader](src/core/segment_reader.rs).
snapshot of the index at one point of time, by holding a list of [SegmentReader](src/index/segment_reader.rs).
In other words, regardless of commits, file garbage collection, or segment merge that might happen, as long as the user holds and reuse the same [Searcher](src/core/searcher.rs), search will happen on an immutable snapshot of the index.
+3 -2
View File
@@ -99,9 +99,10 @@ This is a product decision.
The user can still target the JSON field by specifying its name explicitly:
`json_dynamic.text:hello`.
## Range queries are not supported
## `RangeQuery` requires a fast field
Json field do not support range queries.
`RangeQuery` on a json field is only supported if the field is `FAST`, and only for
string, numeric and date values. Otherwise it returns an `InvalidArgument` error.
## Arrays do not work like nested object