Tonic Structural differences and limitations with Databricks

Required license: Professional or Enterprise

No data science mode

Databricks is only available for data generation workspaces. You cannot use Databricks in a data science mode workspace.

No workspace inheritance

Databricks workspaces do not support workspace inheritance.

Table mode limitations

You can only assign the De-Identify or Truncate table modes.

For Truncate mode, the table is ignored completely. The table does not exist in the destination database.

Generator limitations

Based on the version of Databricks, a Databricks workspace can only use the following generators:

Databricks 10.4 and earlierDatabricks 11.3 and later

Address Alphanumeric String Key ASCII Key Business Name Categorical Character Scramble Character Substitution Company Name Conditional Constant Continuous Custom Categorical Date Truncation Email File Name Find and Replace FNR Geo HIPAA Address Hostname Integer Key IP Address MAC Address Name Noise Generator Null Numeric String Key Phone Random Boolean Random Double Random Hash Random Integer Random Timestamp Random UUID Regex Mask Sequential Integer Shipping Container SSN Struct Mask Timestamp Shift Unique Email URL UUID Key XML Mask

Address Business Name

Categorical

Character Scramble

Company Name

Conditional

Constant

Continuous

Custom Categorical

Date Truncation

Email

FNR

HIPAA Address

Integer Key

IP Address

JSON Mask

MAC Address

Name

Noise Generator

Null

Random Double

Random Hash

Random Integer

Random UUID Regex Mask

SSN

Struct Mask

Timestamp Shift Generator

UUID Key

No subsetting, but support for table filtering

Databricks workspaces do not support subsetting.

However, for tables that use the De-Identify table mode, you can provide a WHERE clause to filter the table. For details, go to Using table filtering for data warehouses and Spark-based data connectors.

No upsert

Databricks workspaces do not support upsert.

Cannot write destination data to container artifacts

For Databricks workspaces, you cannot write the destination data to container artifacts.

Last updated