Skip to main content

SYS.PROJECT.JOBS

The sys.project.jobs table contains the metadata for the jobs in a project. This table only includes the jobs that are being executed at the time that this system table is queried. To get the history of jobs, see sys.project.history.jobs.

Syntax
SELECT * 
FROM sys.project.jobs

Example Output

job_idstatusquery_typeuser_namequeried_datasetsscanned_datasetsattempt_countsubmitted_tsattempt_started_tsmetadata_retrieval_tsplanning_start_tsquery_enqueued_tsengine_start_tsexecution_planning_tsexecution_start_tsfinal_state_tssubmitted_epoch_millisattempt_started_epoch_millismetadata_retrieval_epoch_millisplanning_start_epoch_millisquery_enqueued_epoch_millisengine_start_epoch_millisexecution_planning_epoch_millisexecution_start_epoch_millisfinal_state_epoch_millisplanner_estimated_costrows_scannedbytes_scannedrows_returnedbytes_returnedacceleratedengineerror_msgqueryis_profile_incomplete
1e011d6d-722e-7cc6-2b99-ec4c36b1d400RUNNINGUI_RUNtest_user@dremio.com[sys.project.jobs]empty text12022-02-05 20:48:18.1872022-02-05 20:48:18.1872022-02-05 20:48:18.2732022-02-05 20:48:18.7492022-02-05 20:48:18.8031970-01-01 00:00:00.0002022-02-05 20:48:18.8132022-02-05 20:48:18.8761970-01-01 00:00:00.0001644094098187164409409818716440940982731644094098749164409409880301644094098813164409409887603.8150000035E90000falseFirst Engineempty textSELECT * FROM sys.project.jobsfalse

Fields

FieldData TypeDescription
job_idvarcharThe UUID to identify the job.
statusvarcharThe state of the job.
Enum: SETUP, QUEUED, ENGINE START, RUNNING
query_typevarcharThe mechanism used to submit the job.
Enum: ACCELERATOR_CREATE, ACCELERATOR_DROP, ACCELERATOR_EXPLAIN, FLIGHT,INTERNAL_ICEBERG_METADATA_DROP, JDBC, UI_EXPORT, UI_INTERNAL_PREVIEW, UI_INTERNAL_RUN, UI_PREVIEW, UI_RUN, METADATA_REFRESH, ODBC, PREPARE_INTERNAL, REST, UNKNOWN
user_namevarcharThe username of the user who submitted the job. For jobs that are triggered by Dremio, this value is $dremio$.
queried_datasets[varchar]An array representation of the fully-qualified dataset (table and view) names referenced by the job.
scanned_datasets[varchar]An array representation of the fully-qualified table names or reflection IDs scanned during the process.
Note: The scanned datasets are often different from the queried_datasets.
attempt_countintegerThe number of attempts that the job was attempted.
submitted_tstimestampThe date and time when the job was submitted to the system.
attempt_started_tstimestampThe date and time when latest attempt of the job was started. In most cases, this will be the same value as submitted_ts.
metadata_retrieval_tstimestampThe date and time when the metadata retrieval phase of the job started.
planning_start_tstimestampThe date and time when the planning phase of the job started.
query_enqueued_tstimestampThe date and time when the job was first submitted to the engine.
engine_start_tstimestampThe date and time when the engine replica start up was triggered.
execution_planning_tstimestampThe date and time when the execution planning phase of the job started.
execution_start_tstimestampThe date and time when the job started processing on the engine replicas.
final_state_tstimestampThe date and time when the job execution reached a final state (complete, failed, or canceled).
submitted_epoch_millisintegerThe date and time (in milliseconds) when the job was submitted to the system.
attempt_started_epoch_millisintegerThe date and time (in milliseconds) when this attempt started. In most cases, this will be the same value as submitted_epoch.
metadata_retrieval_epoch_millisintegerThe date and time (in milliseconds) when the metadata retrieval phase of the job started.
planning_start_epoch_millisintegerThe date and time (in milliseconds) when the planning phase of the job started.
query_enqueued_epoch_millisintegerThe date and time (in milliseconds) when the job was first submitted to the engine.
engine_start_epoch_millisintegerThe date and time (in milliseconds) when the engine replica start up was triggered.
execution_planning_epoch_millisintegerThe date and time (in milliseconds) when the execution planning phase of the job started.
execution_start_epoch_millisintegerThe date and time (in milliseconds) when the job started processing on the engine replicas.
final_state_epoch_millisintegerThe date and time (in milliseconds) when the job execution reached a final state (complete, failed, or canceled).
planner_estimated_costdoubleThe estimated cost value provided by the planner.
rows_scannedintegerThe sum of rows that were scanned by all the scans in the job.
bytes_scannedintegerThe sum of the bytes that were scanned by all the scans in the job.
rows_returnedintegerThe number of rows returned by the job.
bytes_returnedintegerThe number of bytes returned by the job results.
acceleratedBooleanThis value will be true if the job was accelerated by a reflection; false otherwise.
enginevarcharThe name of the engine that the job is executing on.
error_msgvarcharThis value will contain the error message that resulted from the job if the job failed; "" otherwise.
queryvarcharThe SQL query that was submitted.
is_profile_incompleteBooleanIf the job has incomplete telemetry data, true. Otherwise, false.