[improve](information schema) introduce routine load job system table (#48963) #49284
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…apache#48963) Part IV of apache#48511 doc apache/doris-website#2196 **Introduce routine load job statistic system table:** ``` mysql> show create table information_schema.routine_load_job\G *************************** 1. row *************************** Table: routine_load_job Create Table: CREATE TABLE `routine_load_job` ( `JOB_ID` text NULL, `JOB_NAME` text NULL, `CREATE_TIME` text NULL, `PAUSE_TIME` text NULL, `END_TIME` text NULL, `DB_NAME` text NULL, `TABLE_NAME` text NULL, `STATE` text NULL, `CURRENT_TASK_NUM` text NULL, `JOB_PROPERTIES` text NULL, `DATA_SOURCE_PROPERTIES` text NULL, `CUSTOM_PROPERTIES` text NULL, `STATISTIC` text NULL, `PROGRESS` text NULL, `LAG` text NULL, `REASON_OF_STATE_CHANGED` text NULL, `ERROR_LOG_URLS` text NULL, `USER_NAME` text NULL, `CURRENT_ABORT_TASK_NUM` int NULL, `IS_ABNORMAL_PAUSE` boolean NULL ) ENGINE=SCHEMA; 1 row in set (0.00 sec) ``` **There are some benefits to empower job with SQL query capability for statistical information:** - It can be used in conjunction with metrics add through apache#48209 to roughly locate abnormal jobs when Grafana alarms, and the following SQL can be used: ``` SELECT JOB_NAME FROM information_schema.routine_load_job_statistics WHERE CURRENT_ABORT_TASK_NUM > 0 OR IS_ABNORMAL_PAUSE = TRUE; ``` - User can use the `select * from information_schema.routine_load_job` instead of the `show routine load`. The advantage is that the `show routine load` can only be searched by name, but SQL can be very flexible in locating jobs
Contributor
Author
|
run buildall |
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
TPC-H: Total hot run time: 40083 ms |
TPC-DS: Total hot run time: 196662 ms |
ClickBench: Total hot run time: 33.32 s |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
|
TeamCity cloud ut coverage result: |
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pick #48963
Part IV of #48511
doc apache/doris-website#2196
Introduce routine load job statistic system table:
There are some benefits to empower job with SQL query capability for statistical information:
select * from information_schema.routine_load_jobinstead of theshow routine load. The advantage is that theshow routine loadcan only be searched by name, but SQL can be very flexible in locating jobsWhat problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)