Does the change feed only publish changes that have been fully replicated, or is it possible to see a document version that will ultimately be the victim of a conflict resolution?
Similar questions I've found that don't quite address this:
How do conflicts affect the Azure Cosmos DB Change Feed in multi-master replication scenarios?
Viewed 198
1 Answers
Currently, change feed only exposes committed changes, tentative changes are not exposed. If a change is done in a satellite (secondary) region, and change feed reads from satellite, the change will get into the feed only after it’s merged in the hub (primary region) and sent back to the satellite. Thus no multiple versions of the same change.
Related