Uh oh!
There was an error while loading. Please reload this page.
branch-4.1: [enhancement](workload policy) Add username-based backend workload policy support #60559 - #64493
Merged
Merged
Conversation
…licy support (#60559) ### What problem does this PR solve? Problem Summary: Before this change, `username` was only treated as an FE-side workload schedule metric. This made it impossible to create or execute workload policies that combine `username` with BE-side metrics such as `query_time`, `be_scan_rows`, `be_scan_bytes`, or `query_be_memory_bytes`. This PR makes `username` a shared workload schedule metric that can be evaluated on both FE and BE: - Add `USERNAME` to `TWorkloadMetricType` so BE policies can receive username conditions. - Pass user metadata from FE fragment params to BE query context for normal query planning and Nereids stream load planning. - Expose user metadata through `TaskController` / `QueryTaskController`. - Add BE-side `WorkloadConditionUsername` evaluation. - Allow FE policy validation to distinguish FE-only metrics, BE-only metrics, and shared metrics. - Keep invalid username conditions rejected, including unsupported operators and blank usernames. - Add unit tests and regression coverage for creating policies with `username` plus BE metrics. ### Release note Support using `username` together with BE-side workload schedule metrics in workload policies. ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [x] Regression test - [x] Unit Test - [x] 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? - [ ] No. - [x] 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 -->
hello-stephen
commented
Jun 15, 2026
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hello-stephen
commented
Jun 15, 2026
Contributor
run buildall |
hello-stephen
commented
Jun 15, 2026
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jun 15, 2026
Contributor
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Jun 15, 2026
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jun 15, 2026
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jun 15, 2026
Contributor
FE Regression Coverage ReportIncrement line coverage |
yiguolei
approved these changes
Jun 16, 2026
ContributorAuthor
PR approved by at least one committer and no changes requested. |
ContributorAuthor
PR approved by anyone and no changes requested. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-picked from #60559