cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

notebook_params deprecation

Keren
New Contributor

In Databricks documentation  for  workflow / Jobs /REST API 2.1 /  Trigger a new job run - some fields in the request body are stated as depreciated, for example notebook_params, jar_params.  In  Jobs REST API 2.2 those fields do not appear at all.

However I can still run Databricks jobs with notebook_params in the body using 2.1 and 2.2

Are these going to be really deprecated?   when?   will there always be backward compatibility as  the notebook_params is in use.  

 

1 REPLY 1

Advika
Databricks Employee
Databricks Employee

Hello @Keren!

Fields like notebook_params and jar_params are deprecated in Jobs REST API 2.1 and no longer appear in 2.2. While an end-of-life date has not been announced yet, it’s recommended to transition to the newer parameter fields rather than relying on deprecated ones for long-term stability.

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now