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: 

Why it still complain REST API version is 2.0 even though set it to 2.1 ?

johnny1
New Contributor II

root@387ece6d15b2:/usr/workspace# databricks --version

Version 0.17.3

root@387ece6d15b2:/usr/workspace# databricks jobs configure --version=2.1

root@387ece6d15b2:/usr/workspace# databricks jobs get --job-id 123

WARN: Your CLI is configured to use Jobs API 2.0. In order to use the latest Jobs features please upgrade to 2.1: 'databricks jobs configure --version=2.1'. Future versions of this CLI will default to the new Jobs API. Learn more at https://docs.databricks.com/dev-tools/cli/jobs-cli.html

Error: b'{"error_code":"INVALID_PARAMETER_VALUE","message":"Job 123 does not exist."}'

root@387ece6d15b2:/usr/workspace#

2 REPLIES 2

johnny1
New Contributor II

Actually ,the document did not help.

I have set the version to 2.1 via command, but it did not take effort .

I am using Databricks client in my own container .

When use it in bare metal , the configuration can take effort , looks very strange?

johnny1
New Contributor II

Command "databricks jobs configure --version=2.1" not work.

workaround with adding option "--version=2.1" to each databricks jobs/runs command .

It is not very convenient.

Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!