Create and trigger a one-time run.
submit_job_and_wait.RdThis is a long-running operation, which blocks until Jobs on Databricks reach
TERMINATED or SKIPPED state with the timeout of 20 minutes, that you can change via timeout parameter.
By default, the state of Databricks Jobs is reported to console. You can change this behavior
by changing the callback parameter.
Usage
submit_job_and_wait(
client,
access_control_list = NULL,
email_notifications = NULL,
git_source = NULL,
health = NULL,
idempotency_token = NULL,
notification_settings = NULL,
queue = NULL,
run_name = NULL,
tasks = NULL,
timeout_seconds = NULL,
webhook_notifications = NULL,
timeout = 20,
callback = cli_reporter
)Arguments
- client
Required. Instance of DatabricksClient()
- access_control_list
List of permissions to set on the job.
- email_notifications
An optional set of email addresses notified when the run begins or completes.
- git_source
An optional specification for a remote Git repository containing the source code used by tasks.
- health
An optional set of health rules that can be defined for this job.
- idempotency_token
An optional token that can be used to guarantee the idempotency of job run requests.
- notification_settings
Optional notification settings that are used when sending notifications to each of the
email_notificationsandwebhook_notificationsfor this run.- queue
The queue settings of the one-time run.
- run_name
An optional name for the run.
- tasks
This field has no description yet.
- timeout_seconds
An optional timeout applied to each run of this job.
- webhook_notifications
A collection of system notification IDs to notify when the run begins or completes.
- timeout
Time to wait for the operation to complete in minutes.
- callback
Function to report the status of the operation. By default, it reports to console.