Hi, I'm Bolo!
What would you like to know?
ASK BOLOPreview
Please to access Bolo.

Table of Contents

Search

  1. Introduction to Databricks Delta Connector
  2. Connections for Databricks Delta
  3. Mappings and mapping tasks with Databricks Delta connector
  4. Databricks Delta pushdown optimization (SQL ELT)
  5. Data type reference

Databricks Delta Connector

Databricks Delta Connector

Advanced settings

Advanced settings

The following table describes the advanced connection properties:
Property
Description
Database
The database name that you want to connect to in Databricks Delta.
Optional for SQL warehouse and Databricks clusters.
For Data Integration, if you do not provide a database name, all databases available in the workspace are listed. The value you provide here overrides the database name provided in the
SQL Warehouse JDBC URL
connection property.
JDBC Driver Class Name
The name of the JDBC driver class.
Optional for SQL warehouse and Databricks clusters.
If you do not specify the driver class, the following class name is used as default:
com.simba.spark.jdbc.Driver
Staging Environment
The cloud provider where the Databricks cluster is deployed.
Required for SQL warehouse and Databricks clusters.
Select one of the following options:
  • AWS
  • Azure
  • Personal Staging Location
Default is Personal Staging Location.
You can select the Personal Staging Location as the staging environment instead of Azure or AWS staging environments to stage data locally for mappings and tasks.
You can use a personal staging location only in Linux operating systems. The Databricks cluster properties doesn't apply when you use a personal staging location.
You cannot use personal staging location when you configure mappings in advanced mode.
You cannot switch between clusters once you establish a connection.
Databricks Delta does not support multi-level dependent connection attributes across clusters.

0 COMMENTS

We’d like to hear from you!