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

Finish implementation of plum_db:erase/3 #1

Open
aramallo opened this issue Apr 11, 2023 · 0 comments
Open

Finish implementation of plum_db:erase/3 #1

aramallo opened this issue Apr 11, 2023 · 0 comments

Comments

@aramallo
Copy link
Contributor

At the moment erase leaves an ERASE marker in the local hashtree and its propagated via broadcast tree but not during AAE. This means that if a node didn't get the broadcast it will never get the ERASE marker.

Also at the moment an incoming new value for the key will not be set when an ERASE marker is present.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aramallo