Uh oh!
There was an error while loading. Please reload this page.
[Chore](pipeline) set PipelineFragmentContext::_timeout and adjust dump_pipeline_tasks infomation display - #35328
Conversation
doris-robot
commented
May 24, 2024
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
BiteTheDDDDt
commented
May 24, 2024
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
May 24, 2024
TeamCity be ut coverage result: |
BiteTheDDDDt
commented
May 24, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
May 24, 2024
TPC-H: Total hot run time: 41075 ms |
doris-robot
commented
May 24, 2024
TeamCity be ut coverage result: |
doris-robot
commented
May 24, 2024
TPC-DS: Total hot run time: 167737 ms |
doris-robot
commented
May 24, 2024
ClickBench: Total hot run time: 30.63 s |
PR approved by at least one committer and no changes requested. |
…mp_pipeline_tasks infomation display (#35328) set PipelineFragmentContext::_timeout and adjust dump_pipeline_tasks infomation display
…mp_pipeline_tasks infomation display (apache#35328) set PipelineFragmentContext::_timeout and adjust dump_pipeline_tasks infomation display
…mp_pipeline_tasks infomation display (apache#35328) set PipelineFragmentContext::_timeout and adjust dump_pipeline_tasks infomation display
## Proposed changes Now we use `query_timeout` to set a timeout value for queries. But for pipelineX engine, Doris do not use it so each query will not end before EOS. This PR fix it. pick #35328 <!--Describe your changes.-->
…mp_pipeline_tasks infomation display (apache#35328) set PipelineFragmentContext::_timeout and adjust dump_pipeline_tasks infomation display
Proposed changes
set PipelineFragmentContext::_timeout and adjust dump_pipeline_tasks infomation display
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...