-
Notifications
You must be signed in to change notification settings - Fork 473
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(json): JSON.MSET may update on the old json value #2579
fix(json): JSON.MSET may update on the old json value #2579
Conversation
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.
@poipoiPIO Thanks for your contribution. This PR looks good to me except for adding some comments to explain the reason.
Co-authored-by: hulk <hulk.website@gmail.com> Co-authored-by: Twice <twice@apache.org>
Co-authored-by: Twice <twice@apache.org>
Quality Gate failedFailed conditions See analysis details on SonarCloud Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
Thank y'all for the review! |
…ctly (#2579) Co-authored-by: hulk <hulk.website@gmail.com> Co-authored-by: Twice <twice@apache.org>
Possible fix for #2552, suggested by @VIVALXH
Summary:
This PR extends the JSON.MSet method by temporarily storing modified JSON objects in memory to prevent multiple data rewrites performed on a single key and only then writing the resulting key objects to the batch.