Skip to content

[feat](cloud) Add a config for cloud txn lazy commit fuzzy test (#50314)#50544

Merged
dataroaring merged 1 commit intoapache:branch-3.0from
swjtu-zhanglei:branch-3.0-pick
Apr 30, 2025
Merged

[feat](cloud) Add a config for cloud txn lazy commit fuzzy test (#50314)#50544
dataroaring merged 1 commit intoapache:branch-3.0from
swjtu-zhanglei:branch-3.0-pick

Conversation

@swjtu-zhanglei
Copy link
Contributor

@swjtu-zhanglei swjtu-zhanglei commented Apr 29, 2025

  • when setting enable_cloud_txn_lazy_commit_fuzzy_test=true, commit_txn will be fifty percent using commit_txn_eventually

pick #50314

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

…he#50314)

* when setting `enable_cloud_txn_lazy_commit_fuzzy_test=true`,
`commit_txn` will be fifty percent using `commit_txn_eventually`
@Thearas
Copy link
Contributor

Thearas commented Apr 29, 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?

@swjtu-zhanglei
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

TeamCity cloud ut coverage result:
Function Coverage: 83.08% (1090/1312)
Line Coverage: 66.06% (18036/27304)
Region Coverage: 65.62% (8888/13544)
Branch Coverage: 55.53% (4798/8640)
Coverage Report: http://coverage.selectdb-in.cc/coverage/31295cfce647849e58f130bf2cb9de5aeaa769d1_31295cfce647849e58f130bf2cb9de5aeaa769d1_cloud/report/index.html

@swjtu-zhanglei
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

TeamCity cloud ut coverage result:
Function Coverage: 83.08% (1090/1312)
Line Coverage: 66.03% (18028/27304)
Region Coverage: 65.53% (8875/13544)
Branch Coverage: 55.44% (4790/8640)
Coverage Report: http://coverage.selectdb-in.cc/coverage/31295cfce647849e58f130bf2cb9de5aeaa769d1_31295cfce647849e58f130bf2cb9de5aeaa769d1_cloud/report/index.html

@swjtu-zhanglei
Copy link
Contributor Author

run cloud_p0

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 9124197 into apache:branch-3.0 Apr 30, 2025
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants