Skip to content

branch-4.0: [Chore](scan) set enable_task_executor_in_internal_table conf's default value to true. #58017 #58057

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
Closed
github-actions wants to merge 1 commit into from
Closed

branch-4.0: [Chore](scan) set enable_task_executor_in_internal_table conf's default value to true. #58017 #58057

github-actions wants to merge 1 commit into from

Conversation

@github-actions
Copy link
Contributor

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

Cherry-picked from #58017

@kaka11chen
[Chore](scan) set enable_task_executor_in_internal_table conf's defau…
2f016d5 
…lt value to true. (#58017)

### What problem does this PR solve?

Related PR: #55935, #57833

Problem Summary:

### Release note
Because the time task scheduler timeout issue, in #55935, we set
`enable_task_executor_in_internal_table` conf's default value to true.
in #57833, we fix it for some cases. So in this PR, set
`enable_task_executor_in_internal_table` conf's default value to true.
@github-actions github-actions bot requested a review from yiguolei as a code owner November 15, 2025 09:18
@Thearas
Copy link
Contributor

Thearas commented Nov 15, 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?

@Thearas
Copy link
Contributor

Thearas commented Nov 15, 2025

run buildall

@yiguolei
Copy link
Contributor

yiguolei commented Nov 15, 2025

Pending， we need check if this feature works correctly on master

@yiguolei yiguolei closed this Nov 15, 2025
@doris-robot
Copy link

doris-robot commented Nov 15, 2025

BE UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.83% (18154/34364)
Line Coverage 38.15% (165187/433018)
Region Coverage 33.20% (128347/386570)
Branch Coverage 33.97% (55352/162926)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei Awaiting requested review from yiguolei yiguolei is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@Thearas @yiguolei @doris-robot @kaka11chen