Overwrite All Settings For A Job

Usage

db_jobs_reset(
  job_id,
  name,
  schedule,
  tasks,
  job_clusters = NULL,
  email_notifications = NULL,
  timeout_seconds = NULL,
  max_concurrent_runs = 1,
  access_control_list = NULL,
  git_source = NULL,
  host = db_host(),
  token = db_token(),
  perform_request = TRUE
)

Arguments

job_id: The canonical identifier of the job.
name: Name for the job.
schedule: Instance of cron_schedule().
tasks: Task specifications to be executed by this job. Use job_tasks().
job_clusters: Named list of job cluster specifications (using new_cluster()) that can be shared and reused by tasks of this job. Libraries cannot be declared in a shared job cluster. You must declare dependent libraries in task settings.
email_notifications: Instance of email_notifications().
timeout_seconds: An optional timeout applied to each run of this job. The default behavior is to have no timeout.
max_concurrent_runs: Maximum allowed number of concurrent runs of the job. Set this value if you want to be able to execute multiple runs of the same job concurrently. This setting affects only new runs. This value cannot exceed 1000. Setting this value to 0 causes all new runs to be skipped. The default behavior is to allow only 1 concurrent run.
access_control_list: Instance of access_control_request().
git_source: Optional specification for a remote repository containing the notebooks used by this job's notebook tasks. Instance of git_source().
host: Databricks workspace URL, defaults to calling db_host().
token: Databricks workspace token, defaults to calling db_token().
perform_request: If TRUE (default) the request is performed, if FALSE the httr2 request is returned without being performed.

Overwrite All Settings For A Job

Usage

Arguments

See also