Skip to content

Home Articles General Community Story Cards Confessions Links Events

More

News Training Technologies Members

Log in Join usJoin ReadMeFeed↗

Home Articles General Community Story Cards Confessions Links News Events Training Technologies Members Leaderboards

Loading…

Shared knowledge. Real progress.
A home for the people building what comes next.

Explore

Articles
General
Community
Search

Community

Members
Leaderboards
Achievements
Community guidelines

The essentials

About ReadMeFeed
Privacy
Terms of use
Moderation policy

© 2026 ReadMeFeed. Built for the next conversation.Built by curiosity. Powered by people.

Home Community Create Inbox Profile

ReadMeFeed / Community knowledge

#api-upgrade

Real questions. Useful conversations. Find the people who know your stack.

All Unanswered Has answers Resolved Unresolved

Cards Compact list

Editorial question33.3K views3,434 votes0 answers3,564 following

AI-generated

Change Feed continuity after a failed upgrade to Cosmos DB API v2.0.0 Full Fidelity mode

The goal is to understand whether Cosmos DB Change Feed guarantees exactly‑once processing of pre‑upgrade changes when a move to API v2.0.0 Full Fidelity mode fails and the account reverts to the legacy API. Constraints include the lack of automatic checkpoint migration during version changes, the possibility that a processor already switched to Full Fidelit

full-fidelity change-feed

cosmosdbTasadduq Burneyowner25K rep · 29 Nov 2025, 17:31 UTC