You need to react to every new or updated item in Cosmos DB to refresh embeddings. Which feature fits?
Why C is the answer
The change feed processor
The change feed gives you an ordered stream of changes, so you refresh only what changed.
In detail
- The change feed processor reacts to each new or updated item.
- Make the processor safe to repeat.
Use case
An illustrative scenario, not a real incident.
A product feed changes all day, and embeddings must follow. The change feed processor picks up each change, so only those items are re-embedded.
See it in different ways
sequenceDiagram participant A as App participant C as Cosmos DB participant P as Change feed processor participant E as Embedding model A->>C: Create or update item C-->>P: Change P->>E: Text E-->>P: Embedding P->>C: Save the embedding
sequenceDiagram participant C as Cosmos DB participant P as Change feed processor participant M as Embedding model C->>P: New or updated item P->>M: Text M-->>P: Embedding P->>C: Stores the vector
flowchart LR S0["Item changes"] --> S1["Change feed"] --> S2["Processor"] --> S3["Embedding updated"]
Key point: React to changes with the change feed.
Why the other options are wrong
- A. A scheduled export to CSV
- An export is not a reaction to each change.
- B. A manual reindex button
- A manual step does not scale.
- D. A nightly full table scan
- A nightly scan is costly, and it lags behind.