This feature is in Public Preview.
Syncsort helps you break down data silos by integrating legacy, mainframe, and IBM data with Databricks. You can easily pull data from these sources into Delta Lake.
Here are the steps for using Syncsort with Databricks.
Syncsort authenticates with Databricks using a Databricks personal access token. To generate a personal access token, follow the instructions in Generate a personal access token.
Syncsort will write data to an S3 bucket and the Databricks integration cluster will read data from that location. Therefore the integration cluster requires secure access to the S3 bucket.
To access AWS resources, you can launch the Databricks integration cluster with an instance profile. The instance profile should have access to the staging S3 bucket and the target S3 bucket where you want to write the Delta tables. To create an instance profile and configure the integration cluster to use the role, follow the instructions in Secure access to S3 buckets using instance profiles.
As an alternative, you can use IAM credential passthrough, which enables user-specific access to S3 data from a shared cluster.
In the Cluster Mode drop-down, select Standard.
In the Databricks Runtime Version drop-down, select a Databricks runtime version.
spark.databricks.delta.optimizeWrite.enabled true spark.databricks.delta.autoCompact.enabled true
Configure your cluster depending on your integration and scaling needs.
For cluster configuration details, see Cluster configurations.
See Server hostname, port, HTTP path, and JDBC URL for the steps to obtain the JDBC URL and HTTP Path.
To connect a Databricks cluster to Syncsort you need the following JDBC/ODBC connection properties:
- JDBC URL
- HTTP Path
Go to the Databricks and Connect for Big Data login page and follow the instructions.