Skip to content

branch-4.0: [chore] (streamload) add enable stream load profile config #57919 #58029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yiguolei merged 1 commit into from
Nov 15, 2025
Merged

branch-4.0: [chore] (streamload) add enable stream load profile config #57919 #58029

yiguolei merged 1 commit into from
Nov 15, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 14, 2025

Cherry-picked from #57919

@HonestManXin
[chore] (streamload) add enable stream load profile config (#57919)
a43f7a4 
When streamload encounters slow performance issues, we need to enable
the stream load profile.
However, current implementations require users to actively enable it by
setting the stream load HTTP header. On the one hand, the cost of
communicating and configuring with users is relatively high; on the
other hand, the time for problem location will also be extended.
Therefore, a configuration on the FE side is added to dynamically enable
profiling.

Co-authored-by: zhangshixin.1024 <zhangshixin.1024@bytedance.com>
@github-actions github-actions bot requested a review from yiguolei as a code owner November 14, 2025 08:23
@hello-stephen
Copy link
Contributor

hello-stephen commented Nov 14, 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?

@hello-stephen
Copy link
Contributor

hello-stephen commented Nov 14, 2025

run buildall

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

github-actions bot commented Nov 14, 2025

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

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 14, 2025

PR approved by anyone and no changes requested.

@hello-stephen
Copy link
Contributor

hello-stephen commented Nov 14, 2025

FE UT Coverage Report

Increment line coverage 0.00% (0/2) 🎉
Increment coverage report
Complete coverage report

@yiguolei yiguolei closed this Nov 15, 2025
@yiguolei yiguolei reopened this Nov 15, 2025
@yiguolei yiguolei merged commit 5db8330 into branch-4.0 Nov 15, 2025
25 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-57919-branch-4.0 branch November 15, 2025 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hello-stephen @yiguolei @HonestManXin