bugfix: do not flush out routeMap in bucketSearchBatched #80
Conversation
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
nurzhan-saktaganov
force-pushed
the
nsaktaganov_resolve_issue_79
branch
from
e371576 to
2608f09
Compare
While handling bucketsDiscoveryWait response, we wrongly store nil pointer for received bucketIDs if the target bucketID does not belong to a replicaset, whose response is being processed. Closes tarantool#79
nurzhan-saktaganov
force-pushed
the
nsaktaganov_resolve_issue_79
branch
from
2608f09 to
b801f6e
Compare
oleg-jukovec
approved these changes
Sep 15, 2025
palage4a
approved these changes
Sep 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
While handling bucketsDiscoveryWait response,
we wrongly store nil pointer for received bucketIDs
if the target bucketID does not belong to a replicaset,
whose response is being processed.
Closes #79
Unfortunately, no new tests are provided due to limitations of the current testing module.
What has been done? Why? What problem is being solved?
I didn't forget about (remove if it is not applicable):
Related issues: