-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](fe-meta) make FE meta be compatible with branch 2.0 (2.0.2.1 or later) #26048
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
wm1581066
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
… later) (apache#26048) In branch 2.0, we changed the read/write method of AnalysisManager, and rename the image module name to AnalysisMgrV2. So we need to make the same change in master branch, so that user can upgrade Doris from branch-2.0 to master branch. After this PR, user can: - upgrade from 2.0.x(or branch-2.0) to master
… later) (apache#26048) In branch 2.0, we changed the read/write method of AnalysisManager, and rename the image module name to AnalysisMgrV2. So we need to make the same change in master branch, so that user can upgrade Doris from branch-2.0 to master branch. After this PR, user can: - upgrade from 2.0.x(or branch-2.0) to master
… later) (apache#26048) In branch 2.0, we changed the read/write method of AnalysisManager, and rename the image module name to AnalysisMgrV2. So we need to make the same change in master branch, so that user can upgrade Doris from branch-2.0 to master branch. After this PR, user can: - upgrade from 2.0.x(or branch-2.0) to master
Proposed changes
In branch 2.0, we changed the read/write method of AnalysisManager,
and rename the image module name to AnalysisMgrV2.
So we need to make the same change in master branch, so that user
can upgrade Doris from branch-2.0 to master branch.
After this PR, user can:
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...