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

M3: partial indexes #12

Merged
dev merged 3 commits from m3-partial-indexes into main 2026-08-10 20:20:11 +00:00
Conversation 0 Commits 3 Files Changed 6 +16 -5
2 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 55009a429d - Show all commits

10
PLAN.md
View File

@@ -1143,6 +1143,16 @@ has to be its own commit with its own re-recorded scorecard.
contrast, was honestly missing -- refused, with the wrong code (2 where contrast, was honestly missing -- refused, with the wrong code (2 where
mongod says 67) but the right answer. mongod says 67) but the right answer.
**Partial indexes landed**; `partial.json` is 24/24. The filter is consulted
in one place, `build_entries`, so the insert and the remove path cannot
disagree about which documents the index holds -- and `unique` then comes
out right for free. Persisted through a fifth flag bit in
`write_index_catalog` with `catalog_version` still 1. **The planner declines
to read from a partial index**: it holds a subset, so answering a query from
it is only correct when the query implies the filter, and that implication
test is the last step of the row. Too few documents is worse than no index.
Left open with it: `hashed.json` is still 0/18.
**`tests/spec/indexes/` is the gate**, recorded red at 3/39 across 42 cases. **`tests/spec/indexes/` is the gate**, recorded red at 3/39 across 42 cases.
A case there is a *sequence* -- create, insert, read, list -- because an A case there is a *sequence* -- create, insert, read, list -- because an
index outlives a `deleteMany` and every case is about which indexes exist. index outlives a `deleteMany` and every case is about which indexes exist.

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 ## 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 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 The three that passed at the start were the reads a partial index does not
not change: this server builds an index over every document, so a query still change: this server indexed every document, so a query still found
finds everything, which is the whole reason the review called the partial gap everything, which is the whole reason the review called the partial gap
smaller than the `arrayFilters` one. smaller than the `arrayFilters` one.
## What recording it settled ## What recording it settled