fix list tag/edge/tagindex/edgeindex #4616
Merged
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.
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
Description:
fix
list tag/edge/tagindex/edgeindex
logic to display data correctly.Although it was discovered by the enterprise version, the community version also has the same problem.
list tag/edge/tagindex/edgeindex
logic has problems, resulting in display wrong dataThe test case is as follows(used for enterprise version):
3) The master cluster does the following:
4)Then the master cluster starts synchronization
restart sync
At this time, the following results are displayed from the slave cluster
desc tag index fix
The result is displayed correctly
show tag indexes
Dirty data is displayed, and the expected result is consistent with the master cluster
close #1236
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
Affects:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: