topic Re: Databricks asset bundles passing parameters using bundle run which are not declared in Data Engineering

Databricks asset bundles passing parameters using bundle run which are not declared

ashish577 — Thu, 22 Feb 2024 05:59:55 GMT

Hi,

We recently decided to move to databricks asset bundles, one scenario that we are dealing with is we have different parameters passed to the same job which are handled in the notebook. With bundles when I try to pass parameters at runtime(which are not declared anywhere) it throws error saying "variable not defined". I am using cli to call bundle run and trying to pass parameters using --var="<varname=value>". Is there anyway to pass ad-hoc parameters to bundle run like we could with api's?

Re: Databricks asset bundles passing parameters using bundle run which are not declared

ashish577 — Thu, 14 Mar 2024 14:27:15 GMT

Found out we can do it using --params=<comma sep key=value pairs>

However, job needs to have at least 1 param defined to accept parameters

Re: Databricks asset bundles passing parameters using bundle run which are not declared

HrushiM — Thu, 14 Mar 2024 15:38:28 GMT

Following syntax can be used.

databricks bundle run -t ENV --params Param1=Value1,Param2=Value2 Job_Name

Job Definition Parameter may look like this.

Re: Databricks asset bundles passing parameters using bundle run which are not declared

ramy — Wed, 04 Sep 2024 13:12:09 GMT

@ashish577 Just an extension to this, can I deploy a job (not run) with different parameter values ?

something like databricks bundle deploy --params k=v

Re: Databricks asset bundles passing parameters using bundle run which are not declared

TheMinsterKid — Mon, 21 Oct 2024 20:50:35 GMT

When I implemented the above with three params, I received an error:

`Error: no such resource: Param2=Value2,`

I found that adding quotes to the syntax did work:

databricks bundle run --params "param1=value1, param2=value2, param3=value3" job

Hope that helps!