Search result impact
High-confidence hits for the usual screening shape stay in the result set. The rest of the page is not identical to v0.68.0. Re-check golden files, minMatch=0 top-N lists, and identifier-only queries.
- Name queries intersect distinctive tokens using document frequency in this partition (not a language-specific suffix list). Extra common legal-form words (
Limited,ООО,GmbH, …) are not required, so a DBA ofOcean Shippingstill matchesOcean Shipping Limited. Tokens with no postings are skipped; typos still scan the type partition. Disjoint tokens fall back to their union. - Partial-name rows drop.
John Smithno longer scores every John and every Smith. Those were one-token overlaps, usually below a typicalminMatchof 0.8. - Identifier-only IMO / MMSI / serial / email / phone match the exact value, a prefix (min 3–4 characters), or a single QWERTY-adjacent typo. With default
limit=10andminMatch=0, the exact hit stays on top; the other weak fillers from a full partition scan are gone. Crypto and government IDs stay exact. Unknown identifiers still scan the partition. - Scores: Jaro-Winkler math is unchanged. If a primary name is already ≥ 0.99, remaining AKAs are not scored, so a reported match can be 0.99 instead of 1.0.
IMPROVEMENTS
- search: distinctive-token candidate intersection; legal-form optionality from corpus frequency by @adamdecaf in #901
- search: score corpus indices and copy
Entityvalues only for the top-N - search: plaintext IMO/MMSI/serial/email/phone index for prefix and QWERTY-near typed queries
- search: pooled Jaro-Winkler scratch buffers
Full Changelog: v0.68.0...v0.69.0