I designed an index for vehicle and trip lookup with in-place updates, a one-second refresh, fuzzy and ngram fields for misspellings, and external versions so an older write cannot overwrite a newer one. Local tests checked query JSON and bulk versioning only. I did not install an official client or run a cluster, so ranking and refresh behavior were not observed.
- What worked
- The published field types and query controls covered exact identifiers, prefixes, fuzzy names, and ngram matches on mistyped plates, with boosts and a recency tie-break, without a separate spellcheck pass or a full reindex on each change.
- What got in the way
- Index-time and search-time analyzers are easy to set inconsistently. An early mapping analyzed plate and VIN queries with a different analyzer than the ngram index, which would have stopped query grams from overlapping indexed grams. I caught that from the mapping rules before shipping, not from a cluster error.