Skip to content

[Chore](fuzzy) do not use pr id to decide wheather enable some fuzzy#46895

Merged
BiteTheDDDDt merged 1 commit intoapache:masterfrom
BiteTheDDDDt:dev_0113
Jan 14, 2025
Merged

[Chore](fuzzy) do not use pr id to decide wheather enable some fuzzy#46895
BiteTheDDDDt merged 1 commit intoapache:masterfrom
BiteTheDDDDt:dev_0113

Conversation

@BiteTheDDDDt
Copy link
Contributor

@BiteTheDDDDt BiteTheDDDDt commented Jan 13, 2025

What problem does this PR solve?

do not use pr id to decide wheather enable some fuzzy

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

@hello-stephen
Copy link
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?

@BiteTheDDDDt
Copy link
Contributor Author

run buildall

Copy link
Collaborator

@shuke987 shuke987 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
Copy link
Contributor

PR approved by anyone and no changes requested.

@BiteTheDDDDt BiteTheDDDDt merged commit 532a839 into apache:master Jan 14, 2025
@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Jan 14, 2025
@github-actions
Copy link
Contributor

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

lzyy2024 pushed a commit to lzyy2024/doris that referenced this pull request Feb 21, 2025
…pache#46895)

### What problem does this PR solve?
do not use pr id to decide wheather enable some fuzzy
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