Fix multi level sg creation bug#5851
Merged
qiaojialin merged 3 commits intoapache:masterfrom May 10, 2022
Merged
Conversation
qiaojialin
approved these changes
May 10, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Cause
The storage group info management of dataNode went wrong when createSchemaRegion. The localStorageGroupSchemaManager go through the auto create sg logic with normal path rather than specified storage group path. It means when the target storage group path is root.a.sg, the sg created by ensureStorageGroup method is root.a since the default sg level is 1.
Solution
rewrite the logic of localStorageGroupSchemaManager.ensureStorageGroup
rename it to ensureStorageGroupByStorageGroupPath
Result screenshot