Skip to content

Conversation

@BiteTheDDDDt
Copy link
Contributor

@BiteTheDDDDt BiteTheDDDDt commented Aug 20, 2025

What problem does this PR solve?

related with #50181

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 Aug 20, 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?

@BiteTheDDDDt
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 94.74% (18/19) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 59.58% (16780/28164)
Line Coverage 48.51% (152640/314687)
Region Coverage 37.47% (116040/309648)
Branch Coverage 40.39% (51236/126859)

@wm1581066 wm1581066 added usercase Important user case type label dev/2.1.x dev/3.0.x dev/3.1.x labels Aug 20, 2025
@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (19/19) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 82.00% (22628/27596)
Line Coverage 74.72% (235014/314524)
Region Coverage 61.87% (194969/315116)
Branch Coverage 66.08% (84459/127822)

@BiteTheDDDDt
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/18) 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (19/19) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 81.96% (22618/27596)
Line Coverage 74.67% (234847/314524)
Region Coverage 61.90% (195046/315116)
Branch Coverage 66.01% (84380/127822)

@BiteTheDDDDt
Copy link
Contributor Author

run buildall

null_map->resize(size);
nested_column->reserve(size);
null_map->resize(begin + size);
nested_column->reserve(begin + size);
Copy link
Contributor

Choose a reason for hiding this comment

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

why here reserve not resize like null map?

@BiteTheDDDDt
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 90.00% (9/10) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 59.58% (16779/28164)
Line Coverage 48.50% (152622/314680)
Region Coverage 37.49% (116085/309645)
Branch Coverage 40.39% (51233/126853)

const auto size = rhs.null_map->size();
null_map->resize(size);
nested_column->reserve(size);
null_map->resize(begin + size);
Copy link
Contributor

Choose a reason for hiding this comment

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

insert_range_from()

@BiteTheDDDDt
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 66.67% (2/3) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 59.58% (16781/28165)
Line Coverage 48.50% (152605/314663)
Region Coverage 37.47% (116028/309641)
Branch Coverage 40.38% (51217/126849)

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (3/3) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 81.94% (22613/27597)
Line Coverage 74.62% (234687/314504)
Region Coverage 61.89% (195042/315136)
Branch Coverage 66.06% (84430/127816)

@hello-stephen
Copy link
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (3/3) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 82.12% (22663/27597)
Line Coverage 74.82% (235305/314504)
Region Coverage 62.08% (195634/315136)
Branch Coverage 66.26% (84696/127816)

Copy link
Contributor

@HappenLee HappenLee 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 Aug 22, 2025
@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

PR approved by anyone and no changes requested.

@BiteTheDDDDt BiteTheDDDDt merged commit 7f0785d into apache:master Aug 22, 2025
27 of 28 checks passed
yiguolei pushed a commit that referenced this pull request Aug 30, 2025
@morrySnow morrySnow mentioned this pull request Sep 22, 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.12-merged dev/3.0.9-merged dev/3.1.1-merged reviewed usercase Important user case type label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants