[CLIENT-3264] Modify on_locking_only batch code to only write info4 byte when on_locking_only is true. #716
Conversation
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #716 +/- ##
==========================================
+ Coverage 81.07% 81.09% +0.01%
==========================================
Files 102 102
Lines 15194 15203 +9
==========================================
+ Hits 12319 12329 +10
+ Misses 2875 2874 -1 ☔ View full report in Codecov by Sentry. |
justinlee-aerospike
approved these changes
Jan 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 preserves compatibility with older servers that do not support the extra info4 byte."
Build artifacts passes, valgrind shows no memory errors, massif memory usage looks ok.