AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.
Rust agent-memoryai-agentsbm25claude-codeclicode-searchcursordatabaseelasticsearchfull-text-searchhybrid-searchjsonllocal-firstmcpmcp-servermodel-context-protocolragrustsearch-enginevector-search
docs(changelog): state what each scroll creation site actually stored (#414)
xerj-orge8a494ca868d
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 682674069..cf0dc12d5 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -12,10 +12,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0- **A multi-index `scroll` reported the wrong `_index` on every continuationpage, so `(_index, _id)` stopped being distinct**([#414](https://github.com/xerj-org/xerj/issues/414)). The scroll context- stored bare hits plus one context-level `index` — `index_names.first()` — and- every page after the first stamped that single name onto every hit. Page one- was correct, because it maps the real per-hit index, so the divergence only- appeared once paging crossed into the second index.+ stored bare hits plus one context-level `index`, and every page after the first+ stamped that single name onto every hit. Page one was correct, because it maps+ the real per-hit index, so the divergence only appeared once paging crossed+ into the second index.++ The two context-creation sites stored *different* wrong values, which is why+ the symptom has two faces: `search_impl` (`/{a,b}/_search?scroll=`) stored+ `index_names.first()`, so hits were labelled with the first concrete index+ (`mi_a`), while `search_with_scroll` (`/{spec}/_search_scroll`) stored the raw+ path spec, so hits were labelled with the un-split string — the+ `_index: "sa,sb"` that #414 reported, 11,900 of 12,000 hits.Ids routinely collide across indices (each numbers its own documents), so aconsumer keyed on `(_index, _id)` silently kept a fraction of the corpus.