Description
Used to return the job history of all ongoing and historical refreshes. Currently, only the most recent 10,000 records from the past 7 days will be displayed. The results can show how many incremental refreshes there are, whether it is an incremental refresh, etc.
Syntax
Parameter Description
WHERE <expr>: (Optional) Allows users to filter based on the fields displayed by theSHOW JOBScommand. Users can use expressions to filter the results for more precise data retrieval.LIMIT num: (Optional) Limits the number of job records returned, ranging from 1-10000.
Return Results
| Field | Description |
|---|---|
| workspace_name | Workspace name |
| schema_name | Schema name |
| name | Dynamic table name |
| virtual_cluster | Computing cluster used |
| start_time | Refresh start time, timestamp type |
| end_time | Refresh end time, timestamp type |
| duration | Refresh duration, interval type |
| state | Job status |
| refresh_trigger | MANUAL (manually triggered by user, including studio scheduling) SYSTEM_SCHEDULED (scheduled by lakehouse) |
| suspended_reson | Reserved field with no special meaning |
| refresh_mode | NO_DATA FULL INCREMENTAL |
| error_message | Information on refresh failure |
| source_tables | Records the base table names used by the dynamic table |
| stats | Information on incremental refresh counts |
| completion_target | Reserved field with no special meaning |
| job_id | Job ID, clicking on the job ID allows viewing of the job profile |
Example
- Filter the corresponding refresh history based on the dynamic table name
- Filter based on time consumption, filtering out UI elements that take more than one second
- Filter based on computing cluster
- Filter by start time