Azure Cosmos DB now provides the ability to access the change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed). A common pattern to implement eventing patterns is
1. Store every version/change as a separate item
2. Read the change feed to merge/consolidate changes and trigger appropriate actions downstream.
You can also expire old versions using TTL: https://docs.microsoft.com/en-us/azure/cosmos-db/time-to-live
How do I even distinguish between an insert or update? I only need documents that were updated.
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Azure Search Product Team
I need this feature. I decided against a soft delete policy with my app, and now I'm stuck dealing with this Search limitation. I'd really love to see a feature to let me hard delete records from my search index when documents no longer exist in my Cosmos collections.
Work on Bytecode support has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
Why is such an important feature put on the backburner? Would love to hear an update on this.