databricks-cli/bundle/run
Pieter Noordhuis 3a812a61e5
Increase timeout waiting for job run to 1 day (#786)
## Changes

It's not uncommon for job runs to take more than 2 hours. On the client
side, we should not stop waiting for a job to complete if it is
intentionally running for a long time. If a job isn't supposed to run
this long, the user can specify a run timeout in the job specification
itself.

## Tests

n/a
2023-09-19 19:54:24 +00:00
..
output Do not include empty output in job run output (#749) 2023-09-08 09:52:45 +00:00
progress Rename bricks -> databricks (#389) 2023-05-16 18:35:39 +02:00
job.go Increase timeout waiting for job run to 1 day (#786) 2023-09-19 19:54:24 +00:00
keys.go Use interactive prompt to select resource to run if not specified (#762) 2023-09-11 18:03:12 +00:00
keys_test.go Rename bricks -> databricks (#389) 2023-05-16 18:35:39 +02:00
options.go Add development runs (#522) 2023-07-12 08:51:54 +02:00
pipeline.go Use interactive prompt to select resource to run if not specified (#762) 2023-09-11 18:03:12 +00:00
runner.go Use interactive prompt to select resource to run if not specified (#762) 2023-09-11 18:03:12 +00:00
runner_test.go Rename bricks -> databricks (#389) 2023-05-16 18:35:39 +02:00