Support filters (queries) on the Change Feed
For some advanced scenarios and for performance reasons, support filters (queries) on the Change Feed
Moving to our backlog (unplanned). Will continue to visit this and update if this changes.
Jared Prather commented
Not having server side filtering is a major gap in the changefeed for large containers. Our containers are a couple terabytes which makes using the changefeed (we run many) wildly inefficient with the amount of data that has to be sent over the wire and de-serialized to only be discarded.
Mario Meyrelles commented
This change is important when we are working with CosmosDB as an Event Store in CQRS/Event Sourcing architectures. I would love to see filtering on Change Feed.
Ste Wilson commented
I agree. With cosmos you are encouraged to put multiple document types into the same collection / partition so they can be update together in a sproc transaction. The down side to this is then you subscribe to that collections change feed and you’re probably going to get a lot of function executions for changes you are not concerned with. This impacts scale and cost making it less viable. A filter on what causes the trigger to fire would solve this.
Alejandro Paz commented
Very important feature to improve perfrmance in change feed consumers.
I'm very keen to see this feature to put in as well.
got my vote!
Cosmos DB should support predicate pushdown for Change Feed so users can filter out documents they don't need.