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: 

i am getting the below error while making a GET request to job in databrick after successfully running it

him
New Contributor III

"error_code": "INVALID_PARAMETER_VALUE",

  "message": "Retrieving the output of runs with multiple tasks is not supported. Please retrieve the output of each individual task run instead."

}Capture

13 REPLIES 13

Debayan
Databricks Employee
Databricks Employee

Looks like the request was malformed (error code: 400) . You can retrieve the details for a single job running GET API.

Please refer: https://docs.databricks.com/dev-tools/api/latest/jobs.html?&_ga=2.42546021.1557771202.1661376549-162...

Could you please provide the body of the request?

him
New Contributor III

Hi debayan ,the body of this request has only job id as key and its value .I am unable to find the solution .can u please provide some other solution to it

CJay
New Contributor III

I believe this is a bug in API 2.1 of Databricks

I had the same issue but after lot of hit and trails I changed the GET url to https://xxxxxxxx.cloud.databricks.com/api/2.0/jobs/runs/get-output?run_id=1863081801 and surprisingly it worked.

know-how
New Contributor III

@CJay thanks for this, your solution to downgrade the API version to 2.0 helped me as well.

Atanu
Databricks Employee
Databricks Employee

Could you please update the API endpoint you are using so that we can check and update you with the same? @Himanshu yadav​ 

Muni
New Contributor II

@Atanu Sarkar​ I belive he is using https://<databricks-instance>/api/2.1/jobs/get-output?run_id=xxxx

Even we are also facing the same problem while retrieving run status.

Can you please check and let us know?

CJay
New Contributor III

try 2.0 instead of 2.1

esfits
New Contributor II

Same issue...switching to 2.0 resolved it. Thanks @Chandrajeet Singh​ 

SANKET
New Contributor II

Use https://<databricks-instance>/api/2.1/jobs/runs/get?run_id=xxxx.

"get-output" gives the details of single run id which is associated with the task but not the Job.

Kris93
New Contributor II

Thanks! That worked in my case

kishanbsh
New Contributor II

I am getting the same issue for the get-output endpoint for both 2.2 and 2.1 versions of the API

https://${databricks-instance}/api/2.2/jobs/runs/get-output?run_id=${run_id}

But interestingly the 2.0 version works like magic

https://${databricks-instance}/api/2.2/jobs/runs/get-output?run_id=${run_id}

Databricks team - Can you look into this and fix this at the earliest?

 

matteomrj
New Contributor II

In order to get the output using the 2.2 API version you should use the task run id instead of the job run id.

Octavian1
Contributor

Hi @Debayan 
I'd suggest to also mention this explicitly in the documentation of the workspace client for get_run_output
One has to pay extra attention to the example

run_id=run.tasks[0].run_id

 otherwise it can be easily missed. 🙂

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