dev/MultiforaDB
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

plan/spec: partial indexes are done, hashed is next

Browse Source 
partial.json 3/24 -> 24/24, hashed.json still 0/18. PLAN §6 records the
planner rule that is deliberately left conservative -- a partial index is
maintained and enforces `unique`, and reads scan until the implication test
exists.

Full matrix at this commit: 250/250 unit tests in ReleaseFast and ReleaseSafe,
83/83 fuzz, operators 125/0, positional 51/0, aggregation 70/0, pinned crud
228/63/196, e2e and crash-fuzz green.
This commit was merged in pull request #12.
This commit is contained in:
A.Shakhmatov
2026-08-10 22:51:38 +03:00
parent f151f13bfc
commit 55009a429d
2 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
tests/spec/indexes/README.md
View File

@@ -37,16 +37,17 @@ first that throws, which is what a client would see.
## Where it stands
Recorded against mongod 8.3.7, run before any of it was implemented:
Recorded against mongod 8.3.7 at 3/39 -- red by construction -- and partial
indexes have since been driven green:
```
hashed.json 0 pass 18 fail 0 skip
partial.json 3 pass 21 fail 0 skip
partial.json 24 pass 0 fail 0 skip
```
Red by construction. The three that pass are the reads a partial index does
not change: this server builds an index over every document, so a query still
finds everything, which is the whole reason the review called the partial gap
The three that passed at the start were the reads a partial index does not
change: this server indexed every document, so a query still found
everything, which is the whole reason the review called the partial gap
smaller than the `arrayFilters` one.
## What recording it settled