Skip to content

branch-2.1: [fix](Nereids) Use the schema saved during planning as the schema of the original target table #47337 #47773

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.

Sign up for GitHub

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

Jump to bottom
Merged
yiguolei merged 1 commit into from
Feb 12, 2025
Merged

branch-2.1: [fix](Nereids) Use the schema saved during planning as the schema of the original target table #47337 #47773

yiguolei merged 1 commit into from
Feb 12, 2025

Conversation

@morrySnow
Copy link
Contributor

@morrySnow morrySnow commented Feb 11, 2025

pick from master #47337

@morrySnow
branch-2.1: [fix](Nereids) Use the schema saved during planning as th…
91f8d4e 
…e schema of the original target table #47337

pick from master #47337

Related PR: #47033 #45045

Problem Summary:

because schema change does not involve recreating the table object, but
rather rebuilding the full schema. So, we should use the schema saved
during planning as the schema of the original target table.
@hello-stephen
Copy link
Contributor

hello-stephen commented Feb 11, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@morrySnow
Copy link
Contributor Author

morrySnow commented Feb 11, 2025

run buildall

@yiguolei yiguolei merged commit 3f1a9db into branch-2.1 Feb 12, 2025
22 of 24 checks passed
morningman pushed a commit to morningman/doris that referenced this pull request Feb 20, 2025
@morrySnow @morningman
branch-2.1: [fix](Nereids) Use the schema saved during planning as th…
6c81bb9 
…e schema of the original target table apache#47337 (apache#47773)

pick from master apache#47337
@CalvinKirs CalvinKirs deleted the 2.1_47337 branch March 28, 2025 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@morrySnow @hello-stephen @yiguolei