Location Connection for Databricks

This section describes the connection details required for creating Databricks location in Fivetran HVR. For information about the pre-requisites, access privileges, and other configuration requirements for creating Databricks location, see Databricks Requirements.

If the managed secrets feature is enabled, option USE TOKEN INSTEAD is displayed in the fields designated for entering secrets.

Field	Description	Equivalent Location Property
CATALOG `Since v6.1.0/33`	Catalog name in a Unity Catalog metastore. If the target database is implemented in the Unity Catalog, and if a value is not supplied in this field, Databricks will use the default catalog hive_metastore.	Databricks_Catalog
DATABASE	Name of the database in Databricks.	Database_Name
SERVER	Hostname or IP-address of the server on which the database in Databricks is running.	Database_Host
PORT	Port number on which the Databricks server is expecting connections.	Database_Port
HTTP PATH	URL for the Databricks compute resource. For more information, refer to Databricks documentation.	Databricks_HTTP_Path
AUTHENTICATION METHOD	Authentication method for connecting HVR to Databricks server. Available options are: User Name and Password : Authenticate using the username and password. Personal Access Token : Authenticate using the Databricks personal access tokens.	Databricks_Authentication_Method
USER	Username for connecting HVR to the database in Databricks.	Database_User
PASSWORD	Password for the USER.	Database_Password

Advanced Settings

Field Description Equivalent Location Property

Field	Description	Equivalent Location Property
LINUX / UNIX ODBC DRIVER MANAGER LIBRARY PATH	Directory path where the ODBC Driver Manager Library is installed. This field is applicable only for Linux/Unix operating system. For a default installation, the ODBC Driver Manager Library is available at /usr/lib64 and does not need to be specified. However, when UnixODBC is installed in for example /opt/unixodbc the value for this field would be /opt/unixodbc/lib.	ODBC_DM_Lib_Path
LINUX / UNIX ODBCINST	Directory path where the odbcinst.ini file is located. This field is applicable only for Linux/Unix operating system. The odbcinst.ini file should contain information about the Simba Spark ODBC Driver under the heading [Simba Spark ODBC Driver 64-bit]. For example: `[Simba Spark ODBC Driver 64-bit] Description=Simba Spark ODBC Driver (64-bit) Driver=/opt/simba/spark/lib/64/libsparkodbc_sb64.so`	ODBC_Inst
ODBC DRIVER	Name of the user defined (installed) ODBC driver used for connecting HVR to the Databricks database.	ODBC_Driver

LINUX / UNIX ODBC DRIVER MANAGER LIBRARY PATH

Directory path where the ODBC Driver Manager Library is installed. This field is applicable only for Linux/Unix operating system.

For a default installation, the ODBC Driver Manager Library is available at /usr/lib64 and does not need to be specified. However, when UnixODBC is installed in for example /opt/unixodbc the value for this field would be /opt/unixodbc/lib.

ODBC_DM_Lib_Path

LINUX / UNIX ODBCINST

Directory path where the odbcinst.ini file is located. This field is applicable only for Linux/Unix operating system.

The odbcinst.ini file should contain information about the Simba Spark ODBC Driver under the heading [Simba Spark ODBC Driver 64-bit]. For example:


[Simba Spark ODBC Driver 64-bit]
Description=Simba Spark ODBC Driver (64-bit)
Driver=/opt/simba/spark/lib/64/libsparkodbc_sb64.so

ODBC_Inst

ODBC DRIVER Name of the user defined (installed) ODBC driver used for connecting HVR to the Databricks database. ODBC_Driver

Staging

HVR supports staging for Databricks location. For information about the location properties for staging, see Staging for Databricks.