Tonic Structural release information

For new workspaces that support it, Data Pipeline V2 is now the default data generation option.

Structural now provides suggested generators for additional sensitivity types such as marital status.

The Protection Audit Trail now includes sensitivity rule events, including when a sensitivity rule is created, edited, or deleted.

Bug fixes and other internal updates.

Fixed an issue that caused a horizontal scrollbar to appear beneath the Privacy Hub sensitive column cards.

Structural no longer requires an external mount to monitor workers.

Bug fixes and other internal updates.

When you create a custom sensitivity rule from the Bulk Edit panel of Database View, you can now choose to apply the generator preset to all of the workspace columns that match the new rule. The Save and Apply option replaces the previous Save and Scan option.

The new environment setting TONIC_DB_SCHEMA configures the Tonic Structural application database schema. Use the new environment setting TONIC_MIGRATION_ENABLE_LOGGING to enable or disable logging when applying migrations to the Tonic Structural application database. Note that if TONIC_DB_SCHEMA is a non-public value, then you must restart the API container. If there was existing data in the Tonic Structural application database, that data is not migrated. After the API is restarted and the migrations are applied, you can import a backup of the existing data.

Bug fixes and other internal updates.

Oracle - When TONIC_ORACLE_SKIP_CREATE_DB is true, tables in the destination database are preserved. If a table filter is provided in TONIC_TABLE_WHITELIST, then destination tables that are not in the whitelist are preserved. Before this change, those tables were truncated.

MongoDB - Added the environment setting TONIC_MONGO_MASK_FIELD_IDS. When set to true, Structural assigns the Mongo ObjectId Key generator to ObjectId field names. Consistency is enabled. The default value is false.

Bug fixes and other internal updates.

Improved error handling for PII detectors.

Google BigQuery - Fixed an issue where some BigQuery workspaces did not release rows from memory in a timely manner.

Bug fixes and other internal updates.

MySQL - The new environment setting TONIC_MYSQL_USE_NATIVE_DUMP_TOOL, when set true, prefers the mysql native tools over the existing default of mariadb.

MySQL - You can now configure the following environment settings to override the Structural default behavior when a connection opens and a session is established:

• TONIC_MYSQL_NETWORK_READ_TIMEOUT
• TONIC_MYSQL_NETWORK_WRITE_TIMEOUT
• TONIC_MYSQL_WAIT_TIMEOUT
• TONIC_MYSQL_LOCK_WAIT_TIMEOUT
• TONIC_MYSQL_INNODB_LOCK_WAIT_TIMEOUT

Azure SSO - Added support for authenticating application service principals using the EntraID client-credentials flow. Service principals can access the Structural API. For configuration requirements, refer to the Azure/EntraID SSO configuration information in the Structural User Guide.

SQL Server - Fixed the copy of stored procedures that reference full-text indexes.

Snowflake - Fixed an issue where, when using the connection string and key-pair authentication options, the test connection button was disabled unless a password was entered.

Updated the legal text that is displayed for new account creation on self-hosted Structural instances.

Structural now supports diagnostic logging for upsert data generation.

For custom sensitivity rules, column matching rules are now always case insensitive. Previously, the column matching rules were always case sensitive.

SQL Server - Added support for:

• Full-Text Search catalogs and indexes
• Change tracking for database and table scopes

‍

Bug fixes and other internal updates.

Improved the free trial onboarding flow. Added to the available data connectors. Fixed an issue with creating a Google BigQuery workspace. Fixed a duplicate display issue.

PostgreSQL - Fixed an issue where Structural failed to process tables that contained a generated column that referenced a user-defined type.

File connector - Fixed an issue that a caused authorization failures when using Assume Role to authorize access to Amazon S3 from Structural Cloud.

Fixed an issue where after an import from a JSON file, Subsetting view did not immediately reflect the state of the workspace.

Spark - Removed support for Livy on Hive.

Scheduling data generation - From the Jobs view (renamed from Job History) for a workspace, you can now configure the data generation to run automatically on a schedule. The schedule consists of one or more cron expressions, along with the time zone to use for the schedule. The Structural API includes new endpoints to manage the job schedule.