-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[fix](routine-load) fix show routine load job result is incorrect #38199
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
1 similar comment
run buildall |
TPC-H: Total hot run time: 39736 ms
|
TPC-DS: Total hot run time: 174246 ms
|
ClickBench: Total hot run time: 30.32 s
|
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. |
run buildall |
run buildall |
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. |
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
TPC-H: Total hot run time: 40266 ms
|
TPC-DS: Total hot run time: 173405 ms
|
ClickBench: Total hot run time: 30.73 s
|
…8199) Use the sql to query routine load records: ``` show routine load for db.job1\G ``` return all routine load job in the db: ``` 10 rows in set (0.02 sec) ``` why the bug happen is there is no correct assignment when analyze the sql: ``` if (Strings.isNullOrEmpty(dbName)) { dbFullName = analyzer.getContext().getDatabase(); if (Strings.isNullOrEmpty(dbFullName)) { ErrorReport.reportAnalysisException(ErrorCode.ERR_NO_DB_ERROR); } } ``` dbFullName will always null if dbName is not null or empty. The bug is introduce by: #27861
Use the sql to query routine load records:
return all routine load job in the db:
why the bug happen is there is no correct assignment when analyze the sql:
dbFullName will always null if dbName is not null or empty.
The bug is introduce by: #27861