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

Explain handling of null keys and values (tombstones) #462

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

embano1
Copy link
Contributor

@embano1 embano1 commented Dec 27, 2024

Closes: #124

Description

Test Steps

Checklist:

  • I have tested my changes. No regression in existing tests.
  • I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closes: awslabs#124
Signed-off-by: Michael Gasch <15986659+embano1@users.noreply.github.com>
@embano1 embano1 requested a review from a team as a code owner December 27, 2024 09:25
@embano1 embano1 changed the title docs: explain handling of null keys and values (tombstones) Explain handling of null keys and values (tombstones) Dec 27, 2024
@embano1 embano1 changed the title Explain handling of null keys and values (tombstones) Explain handling of null keys and values (tombstones) Dec 27, 2024
@embano1 embano1 enabled auto-merge December 27, 2024 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document Tombstone and null keys handling
1 participant