Support Databricks Unity Catalog

[josek]

Please add support for Databricks' Unity Catalog

Currently, when selecting a Databricks-connection in the “Connect In-DB”-tool, and opening the “Query Builder”, only tables in the catalog named “hive_metastore” are listed. That is, Alteryx submits the following SQL query to Databricks:

Listing tables 'catalog : hive\_metastore, schemaPattern : %, tableTypes : null, tableName : %'

However, with Unity Catalog in Databricks the namespace is three-tier and there may be multiple catalogs (and not just the "hive_metastore" catalog), see https://docs.microsoft.com/en-gb/azure/databricks/lakehouse/data-objects#--what-is-a-catalog

I reached out to Alteryx support, which replied that you currently have a feature request for implementing this change (ID TDCB-4056) and they furthermore suggested that I post here.

Thanks in advance.

[renat_isch]

HI @peterma ,

Thanks for your idea suggestion. My name is Renat, I am Alteryx PM responsible for data connectors. Just meant to get back to you and confirm that Alteryx 2023.2 release added support for Databricks Unity Catalog. You can find additional details about Dbx UC at this page: https://help.alteryx.com/current/en/designer/what-s-new-in-designer.html#databricks-unity-catalog-65...

Let me know if you have any questions about the implementation.

Best,

Renat 

[avanibhatnagar]

@phongp & @peterma  - Were you guys able to make this work with select query? What is the catalog name before schema and table name supposed to be?

[peterma]

@avanibhatnagar This should work with select queries on in DB connect tool, you may just need to append on a "cataloguename." to the table name (enthesis may, it seems Alteryx can detect a default catalogue if set by IT on azure, i think?). I don't know what your catalogue will be called as its going to depend on your business setup.