[fix](auth) remove USAGE_PRIV in CatalogPrivEntry when loading meta image from old version#12011
Closed
AshinGau wants to merge 1 commit intoapache:masterfrom
Closed
[fix](auth) remove USAGE_PRIV in CatalogPrivEntry when loading meta image from old version#12011AshinGau wants to merge 1 commit intoapache:masterfrom
AshinGau wants to merge 1 commit intoapache:masterfrom
Conversation
…ge from old version
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
|
Fixed in #12016 |
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
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.
Proposed changes
Problem summary
FE failed when updating from v1.1.2 to master:
This only happened in loading meta image from old version:
GlobalPrivEntry of the previous version does not check 'privs.containsResourcePriv()',
so GlobalPrivEntry maybe contians USAGE_PRIV which is wrong operation and useless priv.
In order to be compatible with this scenario, we should delete USAGE_PRIV.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...