Add a voids_id column for tombstone events#54
Merged
Merged
Conversation
This is our first attempt at supporting deletion. Clients send in an event of type "dimo.tombstone" with a CloudEvent id in the data section. That id gets placed in this new column. We're adding a skipping index to event_type to make it cheaper to find these events. There should not be many.
This was referenced Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is our first attempt at supporting deletion. Clients send in an event of type "dimo.tombstone" with a CloudEvent id in the data section. That id gets placed in a new voids_id column.
We're adding a skipping index to event_type to make it cheaper to find these events. There should not be many.