[doc]update java client link #1270
Merged
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
darionyaphet
previously approved these changes
Nov 14, 2019
darionyaphet
approved these changes
Nov 14, 2019
jude-zhu
approved these changes
Nov 15, 2019
|
Jenkins go |
|
Unit testing passed. |
darionyaphet
previously requested changes
Nov 15, 2019
whitewum
approved these changes
Nov 15, 2019
amber-moe
dismissed
darionyaphet’s stale review
link is the java client repo
|
Unit testing passed. |
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this pull request
Feb 16, 2020
tong-hao
pushed a commit
to tong-hao/nebula
that referenced
this pull request
Jun 1, 2021
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this pull request
Jan 31, 2023
<!-- Thanks for your contribution! In order to review PR more efficiently, please add information according to the template. --> ## What type of PR is this? - [x] bug - [ ] feature - [ ] enhancement ## 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 data The test case is as follows(used for enterprise version): 1) The master cluster is in the synchronous state at the beginning, do the following: ``` show sync status; create tag player1(name string, age int, p3 int, p4 int); stop sync ``` 2) Suppose the slave cluster did the following before synchronizing: ``` create tag index fix on player1(p3); desc tag index fix show tag indexes ```  3） The master cluster does the following: ``` create tag index fix on player1(age); desc tag index fix show tag indexes ```  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 vesoft-inc#1236 ## How do you solve it? ## Special notes for your reviewer, ex. impact of this fix, design document, etc: ## Checklist: Tests: - [ ] Unit test(positive and negative cases) - [ ] Function test - [ ] Performance test - [ ] N/A Affects: - [ ] Documentation affected (Please add the label if documentation needs to be modified.) - [ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.） - [ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).) - [ ] Performance impacted: Consumes more CPU/Memory ## Release notes: Please confirm whether to be reflected in release notes and how to describe: > ex. Fixed the bug ..... Migrated from vesoft-inc#4616 Co-authored-by: panda-sheep <[email protected]>
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.
No description provided.