Skip to content

[branch-4.1][cherry-pick] Drop PredicateColumnType (#64128)#65417

Open
csun5285 wants to merge 1 commit into
apache:branch-4.1from
csun5285:auto-pick-64128-branch-4.1
Open

[branch-4.1][cherry-pick] Drop PredicateColumnType (#64128)#65417
csun5285 wants to merge 1 commit into
apache:branch-4.1from
csun5285:auto-pick-64128-branch-4.1

Conversation

@csun5285

@csun5285 csun5285 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

pick from master #64128

Drop PredicateColumnType

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

None

- Test <!-- At least one of them must be included. -->
    - [ ] Regression test
    - [ ] Unit Test
    - [ ] Manual test (add detailed scripts or steps below)
    - [ ] No need to test or manual test. Explain why:
- [x] 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 <!-- Add your reason?  -->

- Behavior changed:
    - [ ] No.
    - [ ] Yes. <!-- Explain the behavior change -->

- Does this need documentation?
    - [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
apache/doris-website#1214 -->

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
(cherry picked from commit ca4af95)
@csun5285 csun5285 requested a review from yiguolei as a code owner July 9, 2026 09:40
@hello-stephen

Copy link
Copy Markdown
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?

@csun5285

csun5285 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 89.47% (85/95) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.83% (27566/37336)
Line Coverage 57.45% (298995/520487)
Region Coverage 55.09% (251005/455622)
Branch Coverage 56.43% (108659/192555)

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.

2 participants