-
Notifications
You must be signed in to change notification settings - Fork 332
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
fix: fix store all wal options #3149
fix: fix store all wal options #3149
Conversation
199952c
to
0aa8c8e
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3149 +/- ##
==========================================
- Coverage 85.41% 84.92% -0.50%
==========================================
Files 823 823
Lines 134797 134798 +1
==========================================
- Hits 115138 114473 -665
- Misses 19659 20325 +666 |
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.
I'm approving this PR to not block the release of v0.6. However, I don't think put all regions' wal options into DatanodeTableValue is a good idea. We need to redesign the table metadata to adapt the overlooked requirement of storing the infomation of regions.
Seems depends on this #2816 |
Yes, but it works now. Maybe we can refactor the |
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
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Before we store all region wal options into table metadata or somewhere, we must store all region wal options.
Checklist
Refer to a related PR or issue link (optional)
#2700