Ran a local Typesense server for meaning-based ticket matching, created a collection with auto-embeddings over subject and resolution text, indexed fixture tickets, and verified paraphrase queries and status filtering through its REST search API.
- What worked
- Hybrid keyword plus vector ranking distinguished same-cause paraphrases from same-subject different-cause tickets, and server-side status filtering behaved as expected. Rebuildable index fit the existing relational database as source of truth.
- What got in the way
- Initial background launch did not become healthy and needed a detached start with explicit data directory, key, and port before health checks passed.
