โ04-25-2023 12:52 PM
โ04-25-2023 03:05 PM
Turns out there was a webhook but databricks had a bug that made it so it didn't show up in the UI.
The way to find out the offending portion is to look at the json for the job:
The ui is convinced that doesn't exist so you have to use the jobs API to fix it.
import requests
api_base = "https://adb-[redacted].azuredatabricks.net/api/2.0"
databricks_service = "the_o=_part_of_the_url"
# let databricks know the authorization and that we're submitting json
headers = {
"Content-Type": "application/json",
"Authorization": f"Bearer {databricks_token}",
}
# create data for request
data = {
"job_id": {job_id},
"fields_to_remove": ["webhook_notifications"],
}
# submit the rerquest
update_jobs_url = f"{api_base}/jobs/update?o={databricks_service}"
requests.post(update_jobs_url, headers=headers, json=data).text
fix your stuff databricks.
โ04-25-2023 03:05 PM
Turns out there was a webhook but databricks had a bug that made it so it didn't show up in the UI.
The way to find out the offending portion is to look at the json for the job:
The ui is convinced that doesn't exist so you have to use the jobs API to fix it.
import requests
api_base = "https://adb-[redacted].azuredatabricks.net/api/2.0"
databricks_service = "the_o=_part_of_the_url"
# let databricks know the authorization and that we're submitting json
headers = {
"Content-Type": "application/json",
"Authorization": f"Bearer {databricks_token}",
}
# create data for request
data = {
"job_id": {job_id},
"fields_to_remove": ["webhook_notifications"],
}
# submit the rerquest
update_jobs_url = f"{api_base}/jobs/update?o={databricks_service}"
requests.post(update_jobs_url, headers=headers, json=data).text
fix your stuff databricks.
โ09-19-2023 06:39 AM
I had the same issue, thanks for the info! Apparently it's also possible to fix it by removing all the actual notification in the interface (the bugged one is not displayed, but if you remove everything for some reason it removes the bugged one too). I just had to save and put it back after and it worked
Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโt want to miss the chance to attend and share knowledge.
If there isnโt a group near you, start one and help create a community that brings people together.
Request a New Group