Help Center/ Data Lake Insight/ User Guide/ Submitting a SQL Job on the DLI Management Console/ Managing SQL Jobs
Updated on 2026-09-08 GMT+08:00
View PDF
Share

Managing SQL Jobs

Viewing Basic Job Information on the SQL Jobs Page

The SQL Jobs page displays all SQL jobs, which may span multiple pages if there are many jobs. You can navigate to a specific page as needed. DLI allows you to view jobs in all statuses. Jobs in the job list are sorted by creation time in descending order by default.

Table 1 SQL Job management parameters

Parameter

Description

Queues

Name of the queue to which a job belongs

Engine

SQL jobs support the Spark engine.

Spark: displays jobs whose execution engine is Spark.

Username

Name of the user who executed the job.

Type

Job type. The following types are supported:

  • IMPORT: A job that imports data to DLI
  • EXPORT: A job that exports data from DLI
  • DCL: Conventional DCLs and operations related to queue permissions
  • DDL:Conventional DDLs, including creating and deleting databases and tables
  • QUERY: A job that queries data by running SQL statements
  • INSERT: A job that inserts data by running SQL statements
  • UPDATE: A job that updates data.
  • DELETE: A job that deletes a SQL job.
  • DATA_MIGRATION: A job that migrates data.
  • RESTART_QUEUE: A job that restarts a queue.
  • SCALE_QUEUE: A job that changes queue specifications, including sale-out and scale-in.

Status

Job status. Possible values are as follows:

  • Submitting
  • Running
  • Finished
  • Canceled
  • Failed
  • Scaling

Query

SQL statements for operations such as exporting and creating tables

You can click to copy the query statement.

Duration

Running duration of a job

Created

Time when a job is created. Jobs can be displayed in ascending or descending order of the job creation time.

Operation
  • Edit: Edit the job.
  • Cancel
    • You can terminate a job only when the job is in Submitting or Running status.
    • A job whose status is Finished, Failed, or Canceled cannot be terminated.
    • If the Cancel button is gray, you are not allowed to perform this operation.
  • Re-execute: Execute the job again.
  • SparkUI: Display the Spark job execution page.
    NOTE:
    • When you execute a job on a created queue, the cluster is restarted. It takes about 10 minutes. If you click SparkUI before the cluster is created, an empty projectID will be cached. The SparkUI page cannot be displayed. You are advised to use a dedicated queue so that the cluster will not be released. Alternatively, wait for a while after the job is submitted (the cluster is created), and then check SparkUI.
    • You can view only the latest 100 job records on DLI's SparkUI.
  • In addition to the preceding operations, the following operations are available for QUERY jobs and asynchronous DDL jobs.
    • Submit Download Request: Download the results of asynchronous DDL and QUERY statements to a local directory. For details, see Exporting Job Results to a Local Host.
    • View Result: View the job running result.
    • Export Result: Export the job running result to the created OBS bucket.
  • In addition to the preceding operations, the EXPORT job also includes the following operations:
    • Download
  • View Log: Save job logs to the temporary OBS bucket created by DLI.
NOTE:

The View Log button is not available for synchronization jobs and jobs running on the default queue.

Viewing Job Details

On the SQL Jobs page, click next to a job to view its details.

The details displayed vary depending on the job type, status, and configuration options. The console will show the precise information based on these factors. Below are examples for three common job types: load data, create table, and select jobs. For other job types, refer to the console for supported details.

  • For load data jobs (job type: IMPORT), the following details are included: queue, job ID, username, type, status, execution statement, runtime duration, creation time, end time, parameter settings, tags, result count, scanned data volume, scan record count, error record count, storage path, data format, database, table, table headers, delimiter, quote character, escape character, date format, timestamp format, cumulative CPU usage, and output bytes.
  • For create table jobs (job type: DDL), the details include: queue, job ID, username, type, status, execution statement, runtime duration, creation time, end time, parameter settings, tags, result count, scanned data volume, and database.
  • For select jobs (job type: QUERY), the details consist of: queue, job ID, username, type, status, execution statement, runtime duration, creation time, end time, parameter settings, tags, result count (exportable if successful), scanned data volume, executing user, result status (view results if successful; failure reason if failed), database, cumulative CPU usage, and output bytes.
    • Total CPU Used (Core x ms): total CPU used during job execution.
    • Output Bytes: number of output bytes after the job is executed.

Searching for a Job

On the SQL Jobs page, you can search jobs with any of the following operations.

  • Select a queue name.
  • Select an engine.
  • Set the date range.
  • Enter a username, statement, tag, or job ID.
  • Select the creation time in ascending or descending order.
  • Select a job type.
  • Select a job status.
  • Select the job execution duration in ascending or descending order.

Terminating a SQL Job

On the SQL Jobs page, you can click Terminate in the Operation column to stop a submitting or running job.

Parent Topic: Submitting a SQL Job on the DLI Management Console