Skip to content

Conversation

@Tech-Circle-48
Copy link
Contributor

What problem does this PR solve?

Issue Number: close #51625

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 Oct 22, 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?

@Tech-Circle-48
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 80.62% (1647/2043)
Line Coverage 67.01% (29052/43352)
Region Coverage 67.33% (14379/21356)
Branch Coverage 57.70% (7643/13246)

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/287) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.59% (17933/34099)
Line Coverage 37.86% (162692/429759)
Region Coverage 32.28% (124126/384530)
Branch Coverage 33.68% (54370/161452)

@Tech-Circle-48
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 80.62% (1647/2043)
Line Coverage 66.98% (29055/43376)
Region Coverage 67.31% (14382/21368)
Branch Coverage 57.64% (7639/13254)

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 0.00% (0/287) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.59% (17934/34099)
Line Coverage 37.86% (162713/429779)
Region Coverage 32.29% (124177/384536)
Branch Coverage 33.68% (54383/161456)

@Tech-Circle-48
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 80.64% (1649/2045)
Line Coverage 67.01% (29106/43437)
Region Coverage 67.32% (14419/21418)
Branch Coverage 57.70% (7670/13292)

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.

[Feature] Support HTTP Table Valued Function

4 participants