You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.
I'm not able to run dbx execute --cluster-name my-cluster --job job-sample. As far as I understand, in dbx execute, wheel was built, copied to dbfs, and jobs/sample/entrypoint.py was serialized to directly run on the interactive cluster, without providing --conf-file. However the Job class defined in project_name/common.py requires --conf-file, thus exception were thrown
========================================
So far, it seems to me that:
dbx execute is suitable to launch script without external config files, since it's using 1.2 API command execute.
if I want to run the local code on interactive cluster (for fast dev iteration), I'll need a separate job json with "exisiting_cluster_id". then run launch (which is /job/run-now underneath)
The text was updated successfully, but these errors were encountered:
dbx execute is suitable to launch script without external config files, since it's using 1.2 API command execute.
Yes, you're correct in this understanding.
if I want to run the local code on interactive cluster (for fast dev iteration), I'll need a separate job json with "exisiting_cluster_id". then run launch (which is /job/run-now underneath)
I'll provide the functionality to add a default_conf method, which allows you to provide a default configuration inside code for dbx execute-based dev.
I'm not able to run
dbx execute --cluster-name my-cluster --job job-sample
. As far as I understand, indbx execute
, wheel was built, copied to dbfs, andjobs/sample/entrypoint.py
was serialized to directly run on the interactive cluster, without providing--conf-file
. However theJob
class defined inproject_name/common.py
requires--conf-file
, thus exception were thrown========================================
So far, it seems to me that:
The text was updated successfully, but these errors were encountered: