Skip to content

branch-4.1: [fix](fe) Preserve effective Compute Group for audit logs #66281 - #66373

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66281-branch-4.1
Open

branch-4.1: [fix](fe) Preserve effective Compute Group for audit logs #66281#66373
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66281-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #66281

Problem Summary: In Cloud mode, a per-query SET_VAR(cloud_cluster=...)
temporarily changes the session variable used by query scheduling.
StmtExecutor reverted this value before AuditLogHelper built the audit
event, so ComputeGroupName and related per-Compute-Group query, error,
and latency metrics were attributed to the session's original Compute
Group even though the query ran on the hinted group. Preserve the
query-scoped effective Compute Group before reverting SET_VAR and use it
for both audit events and metrics, with fallback to the existing session
resolution path.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner August 3, 2026 06:26
@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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 100.00% (12/12) 🎉
Increment coverage report
Complete coverage report

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