Skip to content

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #59102

…59102)

To analyze SQL patterns across the entire Doris cluster using sql_digest
and implement workload optimization based on SQL patterns, a more
flexible sql_digest generation mechanism is required.

Previously, sql_digest generation was implicitly tied to the
`qe_slow_log_ms` configuration - digests were only generated for queries
considered "slow". This coupling limited flexibility in audit logging.

This PR introduces a new dynamic configuration
`sql_digest_generation_threshold_ms` to optimize the generation of
sql_digest in audit logging.

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### Release note

None

### Check List (For Author)

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

- Behavior changed:
    - [x] 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 December 17, 2025 09:42
@Thearas
Copy link
Contributor

Thearas commented Dec 17, 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?

@dataroaring dataroaring reopened this Dec 17, 2025
@Thearas
Copy link
Contributor

Thearas commented Dec 17, 2025

run buildall

@github-actions
Copy link
Contributor Author

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

@github-actions github-actions bot added approved Indicates a PR has been approved by one committer. reviewed labels Dec 18, 2025
@github-actions
Copy link
Contributor Author

PR approved by anyone and no changes requested.

@yiguolei yiguolei merged commit c628b6d into branch-4.0 Dec 19, 2025
24 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-59102-branch-4.0 branch December 19, 2025 01:39
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