Skip to content

Conversation

@feiniaofeiafei
Copy link
Contributor

@feiniaofeiafei feiniaofeiafei commented May 9, 2025

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #49589

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

@hello-stephen
Copy link
Contributor

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?

@feiniaofeiafei
Copy link
Contributor Author

run buildall

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

github-actions bot commented May 9, 2025

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

@github-actions
Copy link
Contributor

github-actions bot commented May 9, 2025

PR approved by anyone and no changes requested.

@feiniaofeiafei feiniaofeiafei changed the title [fix](test) fix regression test same table name in one databases [fix](test) fix regression test same table name in one database May 9, 2025
@yiguolei yiguolei merged commit e839ec4 into apache:master May 10, 2025
31 of 32 checks passed
yiguolei pushed a commit that referenced this pull request May 10, 2025
…tabase #50737 (#50779)

Cherry-picked from #50737

Co-authored-by: feiniaofeiafei <moailing@selectdb.com>
dataroaring pushed a commit that referenced this pull request May 14, 2025
…tabase #50737 (#50778)

Cherry-picked from #50737

Co-authored-by: feiniaofeiafei <moailing@selectdb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. dev/2.1.10-merged dev/3.0.6-merged p0_test reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants