notebook_params deprecation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2025 08:35 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2025 09:36 AM
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.
