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

M3: the index corpus, recorded red #11

Merged
dev merged 2 commits from m3-index-corpus into main 2026-08-10 19:34:18 +00:00
Conversation 0 Commits 2 Files Changed 8 +8
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 1c098dc48c - Show all commits

8
PLAN.md
View File

@@ -1143,6 +1143,14 @@ 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.
**`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
index outlives a `deleteMany` and every case is about which indexes exist.
Recording it corrected two of the review's own guesses: `$in` in a partial
filter is **allowed** (the review grouped it with `$ne` and `$regex`, which
are 67), and the same key with a different filter and no explicit name is
**IndexKeySpecsConflict (86)**, not 67.
`docs/M3_INDEX_TYPES_DESIGN_REVIEW.md` measures both features' rules and `docs/M3_INDEX_TYPES_DESIGN_REVIEW.md` measures both features' rules and
argues the planner rule that decides the design: a partial index may only argues the planner rule that decides the design: a partial index may only
answer a query whose predicates *imply* its filter, so until that test answer a query whose predicates *imply* its filter, so until that test