Databricks Community

Hello, meanwhile, I've found a workaround to get the owner, or more likely the creator of the dashboard.SELECT request_params.dashboard_id AS dashboard_id, FIRST(user_identity.email) AS owner_email FROM system.access....

Hi @maikel for us databricks extension on vs code to deploy workflow using asset bundles works like a charm. if plugin is not helping out then i suggest you to install databricks CLI separately or point to the one installed together with databricks e...

Hi @liquibricks , I see you said that the materialized view does not exist, so you can't run the ALTER TABLE command. Try to add TBLPROPERTIES ('delta.feature.timestampNtz'='supported') to the MV CREATE statement (or pass it via table_properties in y...

Hi Alesventus,The approach suggested by syzmon_dybczak is definitely the same direction I would go in. To supplement their answer, have a look at this Databricks Labs repository that you may find useful as inspiration (DLT-Meta): https://github.com/d...

you're using ruff for linting. The issue with Databricks magic commands (%sql, %pip, %run) is that they're Databricks-specific syntax, not standard Python, so ruff treats them as errors. you should exclude databricks notebook from ruff.

 Hi, I ran into the same error starting late last week.The issue was caused by dependency version conflicts between my custom package and the libraries preinstalled on the Databricks serverless environment.I fixed it by pinning all my package depende...

Hi Soumitra, this is quite a broad question as it depends on what kind of error you are seeing. If there is something specific, please reply here for something more tailored. In general, when debugging I usually start with the Databricks Assistant as...

If you dont have these resource in dabs already writing/testing configuration might be a good amount of work . with terraform exporter utility you can export all the resource from one workspace as terraform code and deploy it to new workspace quite e...

Thanks @MoJaMa!Originally, I attempted the grant using a SQL Warehouse and it failed. However, I ran again in a notebook using serverless compute and it succeeded. This does appear to resolve the original issue.On a side note, the original error was ...

Strange! That sounds like it might be a DBeaver limitation. I'm glad you got it working and found a workaround!

@Kirankumarbs If you jst want to track Job status Success/Failure, Run Duration, and Costs, use exporter that talks to the Databricks Workspace API or System Tables.grafana/databricks-prometheus-exporter - This is an open-source exporter. It queries ...

How to explain it to the client - The job is operating at the resource ceiling of a very small driver. Tiny, normal day‑to‑day differences (file layout, plan choice, GC timing) sometimes push it over the limit, which is why restarts occasionally “fix...

Cheers !!