Add the API call that will eventually delete the data for a particular user
Add a basic test to see if the user events themselves disappear
Also need to test that query data is removed when deleting users
Uningest the events when a deletion request arrives
Need a method to delete the user event store...
Add an API to delete a list of keys generated by an enumerator
Add a test for the new API call
Implement key deletion for the memory store
Tests for behaviour when keys are missing from the source and for different sets of keys
First pass at an Azure table storage implementation of the deletion operation
Change the 'upper set' test so that it doesn't try to delete a key that doesn't exist
Try catching 404s like with the non-aggregated deletions. Unfortunately this doesn't work as it seems the entire batch is aborted when a record is missing :-/
Remove code to ignore 404s as it just hides the error. Also tried inserting empty entities but Azure doesn't like that if they're part of the same batch
Stop Azure from 404ing on keys that are not in the database by inserting records and then immediately deleting them (this is crazy but it seems to be the only thing you can do that doesn't involve slowly querying each record individually)
Need a test to make sure that deleted events are removed even if the query is not run first (ie, even if the events have not been ingested yet)
Add routine that should delete the events for a particular user
Should return null if a data page is unavailable
Delete the raw events as well
Put the deletion block size in a constant
Add some comments; this file was getting hard to navigate.