refactor(storage): no default sstable info #21845
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 o
2CA0
n 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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Fields in
SstableInfo
is important for data correctness, and we should fill them carefully. HavingDefault
impl forSstableInfo
can easily implicitly fill in unexpected default value.In this PR, we will remove the
derive(Default)
forSstableInfo
when we are not in test build. Current usages of the default implementation are removed and changed accordingly. When dealing withOverlapStrategy
, we used to pass the wholeSstableInfo
, but actually only itskey_range
is used. We will change to only pass theKeyRange
.Checklist
Documentation
Release note