Skip to content

branch-2.1: [Enhancement] reject schema change on hidden columns (#53… #55387

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
Sep 3, 2025
Merged

branch-2.1: [Enhancement] reject schema change on hidden columns (#53… #55387

yiguolei merged 1 commit into from
Sep 3, 2025

Conversation

@codeDing18
Copy link
Contributor

@codeDing18 codeDing18 commented Aug 27, 2025

Issue Number: close #53019

picked from #53376

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason

  • Behavior changed:

    • No.
    • Yes.

  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@codeDing18 codeDing18 requested a review from yiguolei as a code owner August 27, 2025 14:22
@Thearas
Copy link
Contributor

Thearas commented Aug 27, 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?

@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 27, 2025

run buildall

@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 28, 2025

run buildall

@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 29, 2025

run buildall

@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 29, 2025

run buildall

@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 29, 2025

run buildall

@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 30, 2025

run p0

1 similar comment
@codeDing18
Copy link
Contributor Author

codeDing18 commented Aug 30, 2025

run p0

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Sep 1, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Sep 1, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 1, 2025

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit f7e844b into apache:branch-2.1 Sep 3, 2025
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

@starocean999 starocean999 starocean999 approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@codeDing18 @Thearas @yiguolei @starocean999