-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix:HSET support multi feild【wip】 #2930
Open
chejinge
wants to merge
2
commits into
OpenAtomFoundation:unstable
Choose a base branch
from
chejinge:HSET
base: unstable
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
There are no files selected for viewing
This file contains 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.
💡 Codebase verification
Based on the test cases and command definitions, I can now provide a definitive response:
Using HMgetCmd for HGET command is incorrect and breaks Redis compatibility
The test cases in
hash.tcl
clearly show that HGET is designed and expected to:The change from
arity=3
toarity=-3
and usingHMgetCmd
would break this contract and the existing test cases. The testHGET against non existing key
explicitly verifies single field behavior.Recommend reverting the changes as suggested in the original review:
🔗 Analysis chain
Potential issue: HGET should not use HMgetCmd.
Using
HMgetCmd
for theHGET
command appears incorrect:Recommend reverting this change and keeping HGET as a single field operation:
Let's verify the Redis command specifications for HGET:
Let me gather more specific information about the HGET implementation.
The previous search didn't yield much information, so I'm looking for:
This will help us confirm if using HMgetCmd for HGET is indeed problematic or if there's a valid reason for this change.
Let me check the test files to understand the expected behavior of HGET.
I want to verify:
This will help us make a definitive conclusion about whether using HMgetCmd for HGET is correct or not.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 2648
Script:
Length of output: 201
Script:
Length of output: 16706