Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Journaling for dataflow updates #154

Open
rpaul48 opened this issue Dec 1, 2022 · 0 comments
Open

Journaling for dataflow updates #154

rpaul48 opened this issue Dec 1, 2022 · 0 comments
Labels
Futuristic

Comments

@rpaul48
Copy link
Collaborator

rpaul48 commented Dec 1, 2022

In the current implementation of GDPR Forget, a second call to DeleteShard is necessary at the end of ExecForget(). This is because although the initial call to DeleteShard removes all data in the user's shard, subsequent anonymization updates may result in data again being added to the user's shard.

We suspect this is because dataflow updates happen after making changes to the database. So, when we look at the indices, we look at values which are not updated. This may be resolved by implementing journaling for dataflow updates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Futuristic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KinanBab @rpaul48