Skip to main content

DESCRIBE JOB_RUN

Description​

Show the configurations for a specified Job run.

Note that the SQL statement does not end with ;

Syntax​

DESCRIBE JOB_RUN `<job_run_id>`
    JOB_NAME = <string>

Examples​

DESCRIBE JOB_RUN `acde070d-8c4c-4f0d-9d8a-162843c10333`
    JOB_NAME = 'my_job'

Required parameters​

  • <job_run_id>: Specify the ID of the Job run to describe. Note, this should be surrounded by backticks (`), NOT single-quotes.
  • JOB_NAME: Specify the name of the Job that was run.

Status API​

Example Status API response​

The Status API response of the Job description.

{
    "apiStatus": "API_OPERATION_STATUS_SUCCESS",
    "apiResponse": {
        "describeJobRunApiResponse": {
            "sparkJobRun": {
                "id": "<job_run_id>",
                "status": "<job_run_status>",
                "sparkUiEndpoint": "<spark_ui_endpoint>",
                "submittedAt": "YYYY-MM-DDTHH:MM:SS.ssssssZ",
                "endedAt": "YYYY-MM-DDTHH:MM:SS.ssssssZ",
                "sparkJobId": "<spark_job_id>",
                "jobRunUrl": "<job_run_url>",
                "sparkLogsPath": "<spark_logs_path>"
            }
        }
    }
}

Response fields​

  • sparkJobId: The UUID of the parent Job that this run belongs to. Empty string if the parent Job ID is not available.
  • jobRunUrl: A deep-link to the Job run's page in the Onehouse UI. Empty string if a URL is not available.
  • sparkLogsPath: The object-storage directory holding this run's forwarded driver and executor logs (s3:// on AWS, abfss:// on Azure). Empty string if Spark Log Forwarding is not enabled.

The path stops above the source= and date= partitions, so it covers the run's driver and executor logs on every date the run spanned:

s3://onehouse-customer-bucket-ab12cd34/spark-logs/job=daily-ingest/run=0f25bc4f-8a1c-4e2b-9f3d-1a2b3c4d5e6f/

Onehouse records this path when the run is submitted, so it always points to where that run wrote its logs, even if you rename the Job later.