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.

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

SingleDelete #56

Open
marvin-j97 opened this issue May 29, 2024 · 0 comments
Open

SingleDelete #56

marvin-j97 opened this issue May 29, 2024 · 0 comments
Assignees
Labels
api documentation Improvements or additions to documentation enhancement New feature or request examples test

Comments

@marvin-j97
Copy link
Collaborator

marvin-j97 commented May 29, 2024

fjall-rs/lsm-tree#38

Update queue example


SingleDeletes are a very useful operation if any given key is only ever inserted once and never updated (like a Queue)... With standard tombstones, the tombstones would fill up one side of the keyspace, making operations like first_key_value become scan operations until the tombstones are cleaned up by arriving in the last level.

A SingleDelete would vanish when paired with an insert during compaction, causing no tombstone problem, the caveat being that older data is resurrected, so SingleDeletes are only useful for very specific workloads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api documentation Improvements or additions to documentation enhancement New feature or request examples test
Projects
None yet
Development

No branches or pull requests

1 participant