RAG Index Versioning and Blue-Green Retrieval (EXPLAINED)
Hard RAG ops question on index versioning, dual-write, and blue-green cutovers.
TL;DR — Quick Answer
Treat the index as a versioned artifact: build a new index (or namespace) offline, run shadow queries against it, dual-read for a canary cohort, then cut over. Keep the previous version hot for instant rollback and pin prompt configs to index versions.
The Interview Question
How do you version a RAG vector index so you can roll forward or back embeddings, chunking, and metadata without downtime?
Deep Explanation
Sign in to unlock full answer
Get deep explanations, PDF export & all RAG questions
- 4 more sections of deep explanation
- Real-world examples
- Common mistakes
- Interviewer expectations
- Follow-up questions
RAGIndexingVersioningRollbackDatabricksOpenAIAmazon