-
Notifications
You must be signed in to change notification settings - Fork 206
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
feat: map shard id to region id in manifest #645
feat: map shard id to region id in manifest #645
Conversation
44e31f2
to
c9b582d
Compare
c9b582d
to
5847258
Compare
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.
LGTM
Codecov Report
@@ Coverage Diff @@
## main #645 +/- ##
==========================================
+ Coverage 66.44% 66.84% +0.40%
==========================================
Files 283 283
Lines 44286 44006 -280
==========================================
- Hits 29424 29415 -9
+ Misses 14862 14591 -271
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
* expose do_snapshot method in manifest. * Force to do snapshot of manifest when closing table. * map shard id to region id in manifest. * address CR.
Which issue does this PR close?
Closes #
Rationale for this change
Before, manifest is only stored in wal storage, so region id can olny be mapped to table id(otherwise, manifest of specific table will lose after being moved to new shard).
But now, if can mao shard id to region id again because we store the manifest snapshot in oss. We can force it to do snapshot before closing to solve the problem above.
What changes are included in this PR?
See title.
Are there any user-facing changes?
None.
How does this change test
Test by ut.