removes blockstore_meta::ErasureMetaStatus #4310
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
We only need a true/false boolean to tell us if we should try to recover the erasure batch or not. The blockstore_meta::ErasureMetaStatus enum is verbose and redundant.
behzadnouri
force-pushed
the
rm-erasure-meta-status
branch
from
d1758c7 to
3ec49b3
Compare
AshwinSekar
approved these changes
Jan 7, 2025
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.
Problem
We only need a true/false boolean to tell us if we should run the erasure recovery code or not.
The
blockstore_meta::ErasureMetaStatusenum is verbose and redundant.Summary of Changes
Removed
blockstore_meta::ErasureMetaStatus.