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: 

"delta-lake" demo fails with"config" notebook not found when running "00-setup"

RoelofvS
New Contributor III

Hi all,

The delta-lake demo used to run fine for us around October 2024. Reinstalling it now, it fails on initialisation.

Using runtime version 15.4 on a trial Databricks installation, and executing

 

dbdemos.install('delta-lake', overwrite=True, use_current_cluster=True)

 

Frame 2 in 01-Getting-Started-With-Delta-Lake has the line and error:

 

%run ./_resources/00-setup $reset_all_data=false
Notebook not found: Users/[redacted]/Demos/delta-lake/config

 

and indeed it does not exist. Tracing into the 00-setup notebook, the call is definitely there.

Looking at the subsequent frames in notebook 01-Getting-Started-With-Delta-Lake, their outputs are all listed as "Command skipped". This is different to what is usually seen in the demos. Also, none of the other DE demos that I installed give problems - they install and run fine, and show valid outputs for each frame prior to running them myself.

Easiest way to test/reproduce, is to run the install command listed at the top, and to check whether 01-Getting-Started-With-Delta-Lake frame 2 runs or not. 

1 ACCEPTED SOLUTION

Accepted Solutions

brockb
Databricks Employee
Databricks Employee

Hi @RoelofvS , I was able to replicate the issue and reached out to the team that maintains dbdemos, they will get this addressed.

Until that is addressed, you can try manually creating that `config` notebook as follows:

#Note: we do not recommend to change the catalog here as it won't impact all the demo resources such as DLT pipeline and Dashboards.
#Instead, please re-install the demo with a specific catalog and schema using dbdemos.install("lakehouse-retail-c360", catalog="..", schema="...")

catalog = "main__build"
schema = dbName = db = "dbdemos_delta_lake"

volume_name = "delta_lake_raw_data"

 This resolved the issue for me.

View solution in original post

2 REPLIES 2

brockb
Databricks Employee
Databricks Employee

Hi @RoelofvS , I was able to replicate the issue and reached out to the team that maintains dbdemos, they will get this addressed.

Until that is addressed, you can try manually creating that `config` notebook as follows:

#Note: we do not recommend to change the catalog here as it won't impact all the demo resources such as DLT pipeline and Dashboards.
#Instead, please re-install the demo with a specific catalog and schema using dbdemos.install("lakehouse-retail-c360", catalog="..", schema="...")

catalog = "main__build"
schema = dbName = db = "dbdemos_delta_lake"

volume_name = "delta_lake_raw_data"

 This resolved the issue for me.

RoelofvS
New Contributor III

Thank you @brockb, your workaround also works for me.

I found that notebook 03-Delta-Lake-Uniform frame 4 also needed a touch:

CREATE OR REPLACE TABLE main__build.dbdemos_delta_lake.repro1 (
-- CREATE OR REPLACE TABLE workspace.default.repro1

Thank you again.

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