Rollback support using data versioning proposal#32
Open
rjd15372 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ricardo Dias <ricardo.dias@percona.com>
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 RFC proposes implementing rollback support for Valkey through a dual-value data versioning system. The system enables atomic rollback capabilities for multi-step operations by maintaining both committed and uncommitted states for data modifications. This provides a foundation for robust error handling in complex scenarios such as Lua script execution, write-ahead logging, multi-command transactions, and other operations that require all-or-nothing semantics with the ability to safely undo changes when failures occur.