-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[improve](job) Adding FailureReason after manually changing the status of a streaming job #57551
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
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-DS: Total hot run time: 190622 ms |
ClickBench: Total hot run time: 28.06 s |
FE Regression Coverage ReportIncrement line coverage |
sollhui
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 anyone and no changes requested. |
sollhui
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
|
run buildall |
TPC-DS: Total hot run time: 190443 ms |
ClickBench: Total hot run time: 27.53 s |
FE UT Coverage ReportIncrement line coverage |
|
run p0 |
|
run cloud_p0 |
FE Regression Coverage ReportIncrement line coverage |
|
run p0 |
liaoxin01
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. |
…s of a streaming job (#57551) ### What problem does this PR solve? Adding FailureReason after manually changing the status of a streaming job
### What problem does this PR solve? Related PR: #57551 #59784 1. Currently, errors are automatically cleaned up during autoresume. Therefore, if a task continues to generate errors and autoresume, the errors may not be detected at the job level. 2. Data quality errors are flagged when retrieving tasks.
### What problem does this PR solve? Related PR: #57551 #59784 1. Currently, errors are automatically cleaned up during autoresume. Therefore, if a task continues to generate errors and autoresume, the errors may not be detected at the job level. 2. Data quality errors are flagged when retrieving tasks.
What problem does this PR solve?
Adding FailureReason after manually changing the status of a streaming job
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)