Azure-cosmos-dotnet-v2: Track TTL-expired deletes in change feed

[SeanFeldman]

Sililar to the idea brough up at UserVoice.

From CosmosDB team:

We plan to introduce support for tracking deletes in the change feed. Using this capability, you can integrate with Azure Functions or another event processing system to perform operations like execute procedure or call other services programmatically.

[dishakhattri]

Hi, any update on this feature ?

[PhilG112]

Any updates to when this would be available?

[ramumangu]

Any update on this?

[bonserem]

Could really use this issue to remove related GDPR Data from other sources. Might have to move this functionality to outside of CosmosDB otherwise

[tomkuijsten]

It's planned according to uservoice, but that comment was already 18 months ago, @ealsur any news?

[ealsur]

This feature is being worked on. It went back to the design board and it's being worked on again, but no ETA at this moment.

[wpitallo]

Any updates, this will be an awesome feature?

[ealsur]

@mkolt Do we have a rough timeline that can be shared?

@wpitallo Meanwhile, one alternative would be to set a soft delete flag, pickup the change from the Change Feed, then delete the document as part of the Change Feed processing?

[wpitallo]

@ealsur thanks, that is an option, it would be much more elegant though tho have a trigger when the TTL expires. Would rather wait a while if its going to be available soon.

[wpitallo]

@mkolt @ealsur Any updates on this?

[stap123]

Any updates on this, this would be a great feature and would be very useful for GDPR/data retention purposes?

[mkolt]

@wpitallo @stap123 it's coming, check //build conference 2020 for details on availability dates.

[wpitallo]

@mkolt :) awesome do you have a link to the details? Is it being launched at build 2020?

[abaltra]

@wpitallo Hi! was looking forward to some announcement at build2020 around this and didn't see anything. Did I miss it or was this de-prioritized? In any case, any idea if this is coming any time soon?

[tomkuijsten]

You missed it :) https://azure.microsoft.com/en-us/updates/change-feed-with-full-database-operations-for-azure-cosmos-db/

[cwoolum]

It was delayed to 2H 2020 according to UserVoice

[rupeshpatel02]

Any update on this feature

[dsibilio]

+1, any updates on this?

[sdg002]

+1
This will be vital for GDPR compliance. Please, any updates on this?

[vikash001]

+1 any update on this feature.

[MhAllan]

If you are watching this in 2020 hit like! .. Hello, any updates?

[RichMercer]

Over a year after it was announced it's coming and....nothing.

[sdg002]

Still waiting. The absence of "deletes" in change feed has left our data synchronization functionality incomplete. We are forced to do a full sync periodically - a costly operation.

After nearly 2 years working with Cosmos, I have begun to introspect if there is any merit in chosing Cosmos over MSSQL. It looks like Microsoft created Cosmos as a knee jerk reaction to NOSQL protagonists.

Some 10 years ago - Cosmos/NOSQL did make sense.

When I look at at MSSQL in 2020 - I am forced to resign to the conclusion that there is very little that Cosmos or any NOSQL database accomplishes that MSSQL (or any leading RDBMS) cannot fulfill.

The NOSQL world is trying to solve problems which have already have robust solutions in the RDBMS world.