Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #58077

…#58077)

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Function `AI_FILTER` can only match `0` or `1`, which may cause parsing
errors due to the uncertainty of AI returned content, like `0\n` or `\t1
` etc.

Process `AI_SIMILARITY` consistently

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [ ] Regression test
    - [x] 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 <!-- Add your reason?  -->

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

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

### Check List (For Reviewer who merge this PR)

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@github-actions github-actions bot requested a review from yiguolei as a code owner November 18, 2025 08:15
@Thearas
Copy link
Contributor

Thearas commented Nov 18, 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?

@Thearas
Copy link
Contributor

Thearas commented Nov 18, 2025

run buildall

@doris-robot
Copy link

BE UT Coverage Report

Increment line coverage 90.32% (28/31) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.81% (18161/34392)
Line Coverage 38.13% (165305/433522)
Region Coverage 33.16% (128458/387341)
Branch Coverage 33.95% (55380/163112)

@yiguolei yiguolei closed this Nov 20, 2025
@yiguolei yiguolei reopened this Nov 20, 2025
@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Nov 20, 2025
@github-actions
Copy link
Contributor Author

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

@github-actions
Copy link
Contributor Author

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit 6dce942 into branch-4.0 Nov 20, 2025
24 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-58077-branch-4.0 branch November 20, 2025 01:12
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. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants