Upserts, Deletes, and Blue/Green Indexing
Index lifecycle errors create stale or unauthorized answers. A document update can leave old chunks behind; a deletion can leave vectors searchable; an embedding change can mix incompatible spaces. Use versioned chunk sets, transactional updates, or blue/green indexes.
For blue/green, build a new index, reconcile updates, run retrieval and security tests, switch traffic, retain the old index for rollback, then remove it when safe. Track status and counts throughout the process.
Implementation example
Build index B -> validate quality and ACLs -> switch traffic
-> retain index A for rollback -> delete A when safe💡 A staged cutover supports validation and rollback.
Key Takeaways
- Inspect the relevant pipeline stage instead of guessing.
- Preserve source provenance, versions, and access scope.
- Measure quality on representative queries.
Knowledge Check
What is a benefit of blue/green indexing?