Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2022 02:03 AM
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.
