179 questions
No questions match those filters.
How do you keep a RAG knowledge base fresh as source do...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansFreshness in production is a combination of mechanisms, not any single fix. Change detection — file hashing or checking last-modified timestamps — triggers re-indexing only for documents that actually changed, rather than reprocessing the whole corpus on a schedule regardless of what’s different. Versioned embeddings tag each chunk with a version number and timestamp, so retrieval can filter to the current version at query time while old versions stay indexed for audit purposes rather than getting silently overwritten.
Incremental ingestion — tracking document IDs so only new, modified, or deleted documents get processed — becomes essential once a corpus is large enough that full re-embedding on every update would be slow and expensive. Scheduled batch refreshes act as a safety net that catches anything change detection missed, and a TTL on chunks handles content that’s inherently short-lived, auto-expiring instead of quietly going stale. The step that’s easy to skip but catches real drift: periodically sampling a handful of retrieved answers and checking them against the actual source documents, because none of the automated mechanisms above guarantee correctness by themselves — they reduce staleness, they don’t eliminate the need to verify it occasionally.