-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[opt](pipeline) Make pipeline fragment context send_report asynchronized #23142
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.
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
Conversation
e9c319e to
2b51133
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run build all |
2b51133 to
7a855f2
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run build all |
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
run p0 |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run p0 |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run p0 |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run p0 |
3891684 to
776dedd
Compare
|
run p0 |
|
clang-tidy review says "All clean, LGTM! 👍" |
776dedd to
ec727e8
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run p0 |
ec727e8 to
977d03d
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run buildall |
977d03d to
2ac0696
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
2ac0696 to
f62d016
Compare
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
96cbbc8 to
bbc7d5d
Compare
|
run buildall |
bbc7d5d to
341700e
Compare
|
run buildall |
|
TeamCity be ut coverage result: |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
341700e to
3839fc6
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
| } | ||
|
|
||
| Status RuntimeState::query_status() { | ||
| auto st = _query_ctx->exec_status(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why RETURN_IF_ERROR(_query_ctx->exec_status());
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When canceling pipeline fragment context or updating the status of pipeline fragment context, query context will be changed at the same time.
We use this status to try_close or close sink.
HappenLee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
Gabriel39
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Proposed changes
Issue Number: close #xxx
PipelineContextReportExecutorclass to do report asyncrinized.FragmentMgr::trigger_pipeline_context_reportfunc to trigger report.FragmentMgr::trigger_pipeline_context_reportas_report_status_cbofPipelineFragmentContext.StatusofReportStatusRequestfrom reference to constant.exec_statuswhen doing exchange and propagate error info to downstream.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...