Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Why does the DataBricks profile require a 'database'?

See original GitHub issue

I am excited by the included support for DataBricks in v0.9.4

https://github.com/lightdash/lightdash/issues/625

However, I don’t understand why the ‘database’ field is required. In my S3 installation, we just use the ‘schema’ field, and it works fine:

      type: spark
      method: http
      schema: dev_ernest
      host: nauto-biz-prod-us.cloud.databricks.com
      token: _token_
      cluster: 1004-233546-lager607
      port: 443
      connect_timeout: 30
      connect_retries: 15
      threads: 5

Is there some subtlety I am missing? Right now it seems to fail silently, whether or not I put anything in the database field.

Alas, I can’t find any documentation for DataBricks yet:

https://docs.lightdash.com/get-started/setup-lightdash/connect-project#database-1

As a side not, I would love it if LightDash would follow the lead ofthe DBT GitHub Action and pull Warehouse connection data (apart from the token) from the profiles.yml file inside the dbt project:

https://github.com/mwhitaker/dbt-action

Issue Analytics

State:
Created 2 years ago
Comments:23 (2 by maintainers)

Top GitHub Comments

1reaction

owlascommented, May 17, 2022

In the new project settings form, we need to set “database” to “schema” in the UI and move it to the “dbt configuration” just like in https://github.com/lightdash/lightdash/pull/2086