-
Notifications
You must be signed in to change notification settings - Fork 634
feat(string): support IFEQ/IFNE/IFDEQ/IFDNE conditions for SET command #3452
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
Closed
Closed
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
fbd986c
feat(string): support IFEQ/IFNE/IFDEQ/IFDNE conditions for SET command
kirito632 eb4f468
test(cppunit): remove DelEX unit tests from SET PR
kirito632 0ba1990
feat(string): support IFEQ/IFNE/IFDEQ/IFDNE in SET command
kirito632 614b188
Merge branch 'unstable' into feat-set-ifeq
jihuayu 8e46585
Merge branch 'unstable' into feat-set-ifeq
jihuayu b22088c
fix(string): handle uppercase digest and fix NX+GET wrong type behavior
kirito632 aa8e0e3
Merge branch 'origin/feat-set-ifeq' with local fixes for uppercase di…
kirito632 cc078ed
Merge branch 'unstable' into feat-set-ifeq
jihuayu 8a02c75
test(string): remove isolated DelEX tests from SET PR
kirito632 5757c3b
Merge branch 'feat-set-ifeq' of https://github.com/kirito632/kvrocks …
kirito632 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is getting a bit complex. You could try refactoring it in this PR, or open a new PR to refactor it after this one is merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have pushed a new commit that addresses all of them:
Uppercase & Malformed Digests: Added the tests and updated the C++ logic (util::EqualICase and length validation) to handle them correctly.
NX + GET on Wrong Type: I found that the original C++ logic was short-circuiting and returning nil when NX failed, bypassing the GET type check. I have fixed this in redis_string.cc so it now properly returns a WRONGTYPE error, exactly matching Redis standard behavior. The tests pass beautifully now.
Regarding the String::Set refactoring: to keep this PR focused and safe, I will open a separate PR to refactor that function after this one is merged.