Databricks is one of our favorite target connectors that we’ve build into DLH.io over the years.
Not only are customers flocking to Databricks and Unity Catalog as a system but even if they currently use one of the other major cloud warehousing/analytics platforms, they are also picking up Databricks for certain operations and technical capability and realize that DLH.io is the go to solution that just works to get their data in to their databricks system. We follow the Databricks roadmap closely and ensure our customers are enabled for their data needs so they can focus on building great data + AI products.
One small but interesting option in our Databricks target is simply the optional setting to select a Unity Catalog as the target.
Why is this optional?
Well as a carry over from let’s say legacy Databricks when really all we had was the metastore, the default was already set for customers.
With the Unity Catalog introduction and catalog capability going mainstream with customers providing this option in the connector just make sense.
One question we often get is what is my default catalog in Databricks. We wrote an article on that as well so reference the article on How to find my default Unity Catalog in Databricks.
How do I set my Databricks Unity Catalog for data synchronization?
As you create your DLH.io databricks connection you have the option of setting a catalog field.
If you choose to do so this catalog will be the one used for all go-forward data synchronizations and general data access pointer for loading data into your databricks account from 100+ connectors offered by DLH.io
- Access your DLH.io account by logging in with your credentials
- Create or Edit a Databricks connector
- In the field marked “Catalog Name” enter the name of your unity catalog for your workspace
- Save your connection after confirming the other fields accuracy
After setting the catalog, run the Sync Bridge and confirm your data is landing into your target databricks account correctly.
