Skip to content

[Fix](case) Fix test_skip_calc_between_segments when force_olap_table_replication_num=3#48519

Merged
dataroaring merged 1 commit intoapache:masterfrom
bobhan1:fix-DORIS-18974
Mar 4, 2025
Merged

[Fix](case) Fix test_skip_calc_between_segments when force_olap_table_replication_num=3#48519
dataroaring merged 1 commit intoapache:masterfrom
bobhan1:fix-DORIS-18974

Conversation

@bobhan1
Copy link
Contributor

@bobhan1 bobhan1 commented Mar 3, 2025

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

@Thearas
Copy link
Contributor

Thearas commented Mar 3, 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?

@bobhan1
Copy link
Contributor Author

bobhan1 commented Mar 3, 2025

run buildall

@bobhan1
Copy link
Contributor Author

bobhan1 commented Mar 4, 2025

run buildall

Copy link
Contributor

@zhannngchen zhannngchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

github-actions bot commented Mar 4, 2025

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

@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2025

PR approved by anyone and no changes requested.

Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dataroaring dataroaring merged commit 09cbc48 into apache:master Mar 4, 2025
26 of 28 checks passed
github-actions bot pushed a commit that referenced this pull request Mar 4, 2025
github-actions bot pushed a commit that referenced this pull request Mar 4, 2025
yiguolei pushed a commit that referenced this pull request Mar 5, 2025
…orce_olap_table_replication_num=3` #48519 (#48646)

Cherry-picked from #48519

Co-authored-by: bobhan1 <baohan@selectdb.com>
dataroaring pushed a commit that referenced this pull request Mar 10, 2025
…orce_olap_table_replication_num=3` #48519 (#48645)

Cherry-picked from #48519

Co-authored-by: bobhan1 <baohan@selectdb.com>
koarz pushed a commit to koarz/doris that referenced this pull request Jun 4, 2025
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.9-merged dev/3.0.5-merged reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants