Databricks Community

Hi @bryan1, Could you please advise what SDK version are you using?

Unfortunately no, as dashboards are part of the SQL service on the platform they are designed to work with SQL warehouses only, you can create Notebook dashboards that will be able to work with regular clusters but functionalities will be limited in ...

Having same issue...

Yes, it is a good practice to create a separate task for the process_email functionality. This will help in modularizing your code and make it easier to manage and debug. Each task should ideally perform a single responsibility, and separating proces...

I'll try to clear up some misunderstanding surrounding the incremental load feature of materialized views:There isn't a feature to force materialized views to update incrementally. Instead, there is an optimizer called Enzyme that can selectively inc...

Do you have full permissions on this storage location? Also please remember the best practices for Managed tables: You should not use tools outside of Databricks to manipulate files in managed tables directly. You should only interact with data files...

@wt-asw I ran into the same problem, I have provided the table properties at the table declaration as below. Hope this helps!  CREATE OR REFRESH LIVE TABLE silver_table_name_mv TBLPROPERTIES ('delta.feature.timestampNtz' = 'supported') AS SELECT ....

For non Serverless Warehouses are you able to see the tags making it to GCP, I am wondering if the issue might be that as the Serverless warehouse is managed in the Databricks cloud instead of your own cloud this could be the reason why this tags are...

The `RESOURCE_ALREADY_EXISTS` error you're encountering suggests that the primary key constraint `pk_constraint_name` already exists in the target delta table. This constraint may have been created during a previous deployment of the DLT pipeline or ...

In community Edition workspaces the PAT token is not allowed, instead of this you might need to generate an Oauth token to be able to authenticate: https://docs.databricks.com/en/dev-tools/auth/oauth-u2m.htmlYou can refer to the ODBC guide in page 19...

Can you try the approach mentioned in https://ganeshchandrasekaran.com/databricks-how-to-load-data-from-google-drive-github-c98d6b34d1b5 

What is the process you are following to create the PAT token? In community Edition the PAT token is not allowed, instead you need to use Oauth token https://docs.databricks.com/en/dev-tools/auth/oauth-u2m.html