-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](load) Fix the issue of insert into select concurrent reporting causing no error url #49669
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
…causing no error url
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 33977 ms |
TPC-DS: Total hot run time: 192778 ms |
ClickBench: Total hot run time: 30.82 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
dataroaring
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. |
…causing no error url (apache#49669) Fix the issue where concurrent fragment status reporting leads to missing error URLs. For example, when there are two fragments (one scan fragment and one sink fragment), if the sink fragment is canceled due to data quality issues, the scan fragment will also be canceled. However, if the scan fragment reports its status to the Frontend (FE) first but lacks an error URL, the INSERT INTO SELECT operation ultimately fails to return an error URL to the user.
…causing no error url (apache#49669) (apache#3861) cherry-pick from: apache#49669 http://jira.selectdb-in.cc/browse/CIR-14236
…causing no error url (apache#49669) Fix the issue where concurrent fragment status reporting leads to missing error URLs. For example, when there are two fragments (one scan fragment and one sink fragment), if the sink fragment is canceled due to data quality issues, the scan fragment will also be canceled. However, if the scan fragment reports its status to the Frontend (FE) first but lacks an error URL, the INSERT INTO SELECT operation ultimately fails to return an error URL to the user.
…causing no error url (apache#49669) (apache#3917) cherry-pick from: apache#49669 http://jira.selectdb-in.cc/browse/CIR-14236
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Fix the issue where concurrent fragment status reporting leads to missing error URLs. For example, when there are two fragments (one scan fragment and one sink fragment), if the sink fragment is canceled due to data quality issues, the scan fragment will also be canceled. However, if the scan fragment reports its status to the Frontend (FE) first but lacks an error URL, the INSERT INTO SELECT operation ultimately fails to return an error URL to the user.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)