An Azure NoSQL database service for app development.
Hi @Johnston, Anthony,
It appears you're aiming to explore the Cosmos DB change feed manually, without introducing any modifications to the existing codebase.
- While the Azure Portal does not offer a direct interface to manually navigate the change feed, you can inspect data changes and their associated timestamps by querying the container directly. This allows visibility into the latest updates without altering the change feed processor's lease state.
- Implement a Custom Tracking - Instead of modifying lease configurations, implement a custom field—such as a
statusattribute—within your documents to track processing state. This enables efficient filtering of unprocessed entries and facilitates controlled handling of change feed events without altering lease mechanics. - Replica Approach - If direct lease manipulation is a concern, consider maintaining a separate Cosmos DB container or an alternative storage solution such as Azure Blob Storage to log change feed events or processing metadata. This approach allows independent management of processing state and avoids interference with the built-in lease coordination mechanism
- For a resilient and scalable solution, leveraging Azure Functions or a dedicated Change Feed Processor is recommended for handling change feed events. These services offer native support for lease management, ensuring fault tolerance and eliminating the need for manual intervention in lease state coordination.
- Refer document -
https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/change-feed-design-patterns?tabs=latest-version https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/read-change-feed
If you have more detailed information about what you're specifically trying to achieve or concerns regarding the change feed, feel free to share.
Regards,
Vrishabh