[mysqlctl] Restructure MetadataManager
to reduce public API surface area
#8152
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.
Signed-off-by: Andrew Mason amason@slack-corp.com
Description
This is a follow-up PR to address some comments on #8107, just to address the public API surface of
mysqlctl.MetadataManager
.I need to think through a bit more about how to work through the behaviors of
-init_populate_metadata
and-restore_from_backup
to simplify (and hopefully clarify) the checks we currently do inpopulateLocalMetadatLocked
, so I'm going to do that in a second PR.Related Issue(s)
Checklist
Deployment Notes