-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Dss part1: use local id in the space range for tag edge index #2550
Conversation
98ebdc1
to
a058610
Compare
Why need this? |
Data synchronization between clusters |
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.
Reviewed before, LGTM.
Please see the second, compatible with old data |
So now there are independent incremental id in separate spaces, the schema id will be same for different spaces, and this behavior different from before. For more compatible I think you could reuse the Global ID and just store them in the local id key to distinguish the owned space, and in this case the schema id in different space won't be same (they are still generated by global id) |
Fix tagnum is not passed into GITHUB_OUTPUT Co-authored-by: George <58841610+Shinji-IkariG@users.noreply.github.com>
As title
1) Tag, edge, tag index and edge index use space range id.
2) Compatible with the existing old schema creating previously.
Synchronize nebula-storage repo pr vesoft-inc/nebula-storage#501