From 8a4cfc40f5b7446c0700471aa50290dbb7f8ea97 Mon Sep 17 00:00:00 2001 From: ZainnQureshii <43629888+ZainnQureshii@users.noreply.github.com> Date: Sat, 26 Sep 2026 12:04:26 +0200 Subject: [PATCH] Fix stale JSON range query note and ARCHITECTURE.md link Co-Authored-By: Claude Opus 5.5 --- ARCHITECTURE.md | 2 +- doc/src/json.md | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md index 997cb075e..ab1104f24 100644 --- a/ARCHITECTURE.md +++ b/ARCHITECTURE.md @@ -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. diff --git a/doc/src/json.md b/doc/src/json.md index 543004940..b3d10ae51 100644 --- a/doc/src/json.md +++ b/doc/src/json.md @@ -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