Uh oh!
There was an error while loading. Please reload this page.
[feat](load) introduce load job system table - #57421
Merged
Merged
Conversation
sollhui
commented
Oct 28, 2025
ContributorAuthor
run buildall |
Thearas
commented
Oct 28, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
hello-stephen
commented
Oct 28, 2025
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 28, 2025
Contributor
FE Regression Coverage ReportIncrement line coverage |
hello-stephen
commented
Oct 28, 2025
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 28, 2025
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
sollhui
commented
Oct 29, 2025
ContributorAuthor
run performance |
doris-robot
commented
Oct 29, 2025
TPC-DS: Total hot run time: 190987 ms |
doris-robot
commented
Oct 29, 2025
ClickBench: Total hot run time: 28.64 s |
Uh oh!
There was an error while loading. Please reload this page.
dwdwqfwe pushed a commit
to dwdwqfwe/doris
that referenced
this pull request
Oct 31, 2025
### What problem does this PR solve?
Introduce load job statistic system table:
```
mysql> show create table information_schema.load_jobs\G
*************************** 1. row ***************************
Table: load_jobs
Create Table: CREATE TABLE `load_jobs` (
`JOB_ID` text NULL,
`LABEL` text NULL,
`STATE` text NULL,
`PROGRESS` text NULL,
`TYPE` text NULL,
`ETL_INFO` text NULL,
`TASK_INFO` text NULL,
`ERROR_MSG` text NULL,
`CREATE_TIME` text NULL,
`ETL_START_TIME` text NULL,
`ETL_FINISH_TIME` text NULL,
`LOAD_START_TIME` text NULL,
`LOAD_FINISH_TIME` text NULL,
`URL` text NULL,
`JOB_DETAILS` text NULL,
`TRANSACTION_ID` text NULL,
`ERROR_TABLETS` text NULL,
`USER` text NULL,
`COMMENT` text NULL,
`FIRST_ERROR_MSG` text NULL
) ENGINE=SCHEMA;
1 row in set (0.01 sec)
```
User can use the `select * from information_schema.load_jobs` instead of
the `show load`. The advantage is that SQL can be very flexible in
locating jobs.
Example:
```
mysql> SELECT * FROM information_schema.load_jobs WHERE LABEL = 'test_load_job_label_b5347e94f2614e2c92705d6a6824a380'\G
*************************** 1. row ***************************
JOB_ID: 1761643165987
LABEL: test_load_job_label_b5347e94f2614e2c92705d6a6824a380
STATE: FINISHED
PROGRESS: Unknown id: 1761643165987
TYPE: INSERT
ETL_INFO: \N
TASK_INFO: cluster:N/A; timeout(s):14400; max_filter_ratio:0.0
ERROR_MSG: \N
CREATE_TIME: 2025-10-28 17:23:08
ETL_START_TIME: 2025-10-28 17:23:08
ETL_FINISH_TIME: 2025-10-28 17:23:08
LOAD_START_TIME: 2025-10-28 17:23:08
LOAD_FINISH_TIME: 2025-10-28 17:23:09
URL: JOB_DETAILS: {"ScannedRows":1,"LoadBytes":25,"FileNumber":0,"FileSize":0,"TaskNumber":1,"Unfinished backends":[],"All backends":[1754377661179]}
TRANSACTION_ID: 72076
ERROR_TABLETS: {}
USER: root
COMMENT: FIRST_ERROR_MSG:
```sollhui added a commit
to sollhui/doris
that referenced
this pull request
Dec 9, 2025
Introduce load job statistic system table:
```
mysql> show create table information_schema.load_jobs\G
*************************** 1. row ***************************
Table: load_jobs
Create Table: CREATE TABLE `load_jobs` (
`JOB_ID` text NULL,
`LABEL` text NULL,
`STATE` text NULL,
`PROGRESS` text NULL,
`TYPE` text NULL,
`ETL_INFO` text NULL,
`TASK_INFO` text NULL,
`ERROR_MSG` text NULL,
`CREATE_TIME` text NULL,
`ETL_START_TIME` text NULL,
`ETL_FINISH_TIME` text NULL,
`LOAD_START_TIME` text NULL,
`LOAD_FINISH_TIME` text NULL,
`URL` text NULL,
`JOB_DETAILS` text NULL,
`TRANSACTION_ID` text NULL,
`ERROR_TABLETS` text NULL,
`USER` text NULL,
`COMMENT` text NULL,
`FIRST_ERROR_MSG` text NULL
) ENGINE=SCHEMA;
1 row in set (0.01 sec)
```
User can use the `select * from information_schema.load_jobs` instead of
the `show load`. The advantage is that SQL can be very flexible in
locating jobs.
Example:
```
mysql> SELECT * FROM information_schema.load_jobs WHERE LABEL = 'test_load_job_label_b5347e94f2614e2c92705d6a6824a380'\G
*************************** 1. row ***************************
JOB_ID: 1761643165987
LABEL: test_load_job_label_b5347e94f2614e2c92705d6a6824a380
STATE: FINISHED
PROGRESS: Unknown id: 1761643165987
TYPE: INSERT
ETL_INFO: \N
TASK_INFO: cluster:N/A; timeout(s):14400; max_filter_ratio:0.0
ERROR_MSG: \N
CREATE_TIME: 2025-10-28 17:23:08
ETL_START_TIME: 2025-10-28 17:23:08
ETL_FINISH_TIME: 2025-10-28 17:23:08
LOAD_START_TIME: 2025-10-28 17:23:08
LOAD_FINISH_TIME: 2025-10-28 17:23:09
URL:
JOB_DETAILS: {"ScannedRows":1,"LoadBytes":25,"FileNumber":0,"FileSize":0,"TaskNumber":1,"Unfinished backends":[],"All backends":[1754377661179]}
TRANSACTION_ID: 72076
ERROR_TABLETS: {}
USER: root
COMMENT:
FIRST_ERROR_MSG:
```16 tasks
yiguolei pushed a commit
that referenced
this pull request
Dec 11, 2025
…8850) pick #57421 Introduce load job statistic system table: ``` mysql> show create table information_schema.load_jobs\G *************************** 1. row *************************** Table: load_jobs Create Table: CREATE TABLE `load_jobs` ( `JOB_ID` text NULL, `LABEL` text NULL, `STATE` text NULL, `PROGRESS` text NULL, `TYPE` text NULL, `ETL_INFO` text NULL, `TASK_INFO` text NULL, `ERROR_MSG` text NULL, `CREATE_TIME` text NULL, `ETL_START_TIME` text NULL, `ETL_FINISH_TIME` text NULL, `LOAD_START_TIME` text NULL, `LOAD_FINISH_TIME` text NULL, `URL` text NULL, `JOB_DETAILS` text NULL, `TRANSACTION_ID` text NULL, `ERROR_TABLETS` text NULL, `USER` text NULL, `COMMENT` text NULL, `FIRST_ERROR_MSG` text NULL ) ENGINE=SCHEMA; 1 row in set (0.01 sec) ``` User can use the `select * from information_schema.load_jobs` instead of the `show load`. The advantage is that SQL can be very flexible in locating jobs. Example: ``` mysql> SELECT * FROM information_schema.load_jobs WHERE LABEL = 'test_load_job_label_b5347e94f2614e2c92705d6a6824a380'\G *************************** 1. row *************************** JOB_ID: 1761643165987 LABEL: test_load_job_label_b5347e94f2614e2c92705d6a6824a380 STATE: FINISHED PROGRESS: Unknown id: 1761643165987 TYPE: INSERT ETL_INFO: \N TASK_INFO: cluster:N/A; timeout(s):14400; max_filter_ratio:0.0 ERROR_MSG: \N CREATE_TIME: 2025-10-28 17:23:08 ETL_START_TIME: 2025-10-28 17:23:08 ETL_FINISH_TIME: 2025-10-28 17:23:08 LOAD_START_TIME: 2025-10-28 17:23:08 LOAD_FINISH_TIME: 2025-10-28 17:23:09 URL: JOB_DETAILS: {"ScannedRows":1,"LoadBytes":25,"FileNumber":0,"FileSize":0,"TaskNumber":1,"Unfinished backends":[],"All backends":[1754377661179]} TRANSACTION_ID: 72076 ERROR_TABLETS: {} USER: root COMMENT: FIRST_ERROR_MSG: ``` ### What problem does this PR solve? Issue Number: close #xxx Related PR: #xxx Problem Summary: ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into -->
Closed
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
What problem does this PR solve?
Introduce load job statistic system table:
User can use the
select * from information_schema.load_jobsinstead of theshow load. The advantage is that SQL can be very flexible in locating jobs.Example:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)