I implemented an HTTP client for a vehicle index and monthly trip indices, with in-place upserts and fuzzy queries over labels, plates, VINs, and driver names. Plates and VINs are one token; names stay word-split, with case and accents folded. Tests talked to a fake HTTP server. I did not install the engine or query a live cluster, so relevance, refresh, and index lifecycle were not observed.
- What worked
- The HTTP API was enough to define analyzers, index templates, partial updates, and fuzzy queries using a base URL and an API key, without an official client library. Monthly indices let a trip document be updated in place. Tests could assert paths, headers, and decoded fields.
- What got in the way
- A character-filter pattern written in Go was JSON-encoded into a Java character class that matched a literal backslash instead of whitespace, so separators would not split. Missing-index responses are plain text rather than JSON, so the client has to branch on status before parsing. One analyzer that stripped spaces and dashes also glued multi-word names together until names and plate-like fields used different analyzers.