Tonic Structural release information

PostgreSQL - Fixed an issue issue where connection pool limits were not always being respected when creating PostgreSQL connection strings.

Fixed an issue where setting query filter on a non-target subsetting table caused errors.

The Structural API now provides an api/Privacy/history/search endpoint to allow you to issue paginated queries of privacy events. These are the same events that display on the Protection Audit Trail on Privacy Hub.

Bug fixes and other internal updates.

PostgreSQL - Added support for date and time primary keys for subsetting.

Fixed an issue in the Conditional generator where the equality condition for dates was not considered during data generation.

Improved the Business Name generator to avoid unintended or awkward names.

PostgreSQL - Added the environment setting TONIC_USE_SHARED_CONNECTION_FOR_CONSTRAINTS, which allows you to disable the use of a shared connection when applying constraints.

SQL Server - Fixed an issue where sequence values were not updated in the destination database.

File connector - Added support for Avro files that use Zstandard compression.

PostgreSQL - You can now use Document View to configure JSON columns in a PostgreSQL database.

Revised schema change type definition and handling - We have changed how we categorize and respond to detected schema changes.

Sensitive schema changes include schema changes that could result in data leakage. These include new tables and columns, new collections and path types, changes to column data types, and changes to nullability. These types of schema changes always block data generation. Schema Changes view includes options to resolve these changes.

Notifications are schema changes that Structural resolves automatically for each data generation, unless the workspace is configured to block data generation for all schema changes. Notifications include removed tables and columns, removed collections and paths, and changing a column to a foreign key. To permanently resolve these changes, you address them on Schema Changes view.

Fixed an issue where in specific cases when tables had 4 or fewer rows, columns that contained credit card numbers were sometimes not identified as containing sensitive data.

Fixed an issue where very large JSON files returned an error when reading rows during data generation. When Structural reads a JSON schema, it no longer parses the entire file and reads it into memory.

Amazon DynamoDB - The DynamoDB connector is now out of beta.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Fixed an issue where very large JSON files returned an error when read into Document View. When Structural reads a JSON schema, it no longer parses the entire file and reads it into memory.

Structural now ignores columns that are assigned the Continuous generator but that contain constant values, and preserves the original value.

Bug fixes and other internal updates.

Fixed an issue where Structural could not import a JSON file of virtual foreign keys that were previously exported. As of this update, for data connectors that do not support schemas, you cannot provide a schema value.

File connector - For file mounts, removed the environment setting to configure a single file mount location. The file mount location is always configured in the workspace.

Oracle - Removed validation of objects in system schemas.

Oracle - Added logging for object validation errors.

Oracle - Added partial support for reference partitioned tables when managing the destination schema manually.

When you configure a workspace to generate output to a container repository, and you use provided credentials to generate to ECR, you can now optionally provide a session token.

Removed support for the Yugabyte data connector.

Oracle - Fixed an issue where enable trigger statements did not specify the destination schema.

You can now override the following environment settings in individual workspaces:

• TONIC_READ_RANGES_PARALLELISM

• TONIC_PARTITION_PARALLELISM

• TONIC_FILE_GROUP_PARALLELISM

• TONIC_BIGQUERY_READ_PARALLELISM

• TONIC_ORACLE_DATA_PUMP_PARALLELISM

• TONIC_DATABRICKS_SKIP_CREATE_DB

Removed the environment setting TONIC_DATABRICKS_ENABLE_WORKSPACE_SKIP_CREATE_DB, and also deprecated the skipCreateDB workspace property in the Structural API.

Now, to control whether to use your own schema for Databricks, use the setting TONIC_DATABRICKS_SKIP_CREATE_DB, which you can also configure in individual workspaces.

Bug fixes and other internal updates.

Oracle: The Data Pipeline v2 generation flow now waits for materialized views and other objects to be created before it issues GRANT statements that might reference those views and objects.

The encryption and decryption keys for Structural data encryption can now be configured as workspace overrides to the environment settings TONIC_DATA_DECRYPTION_KEY and TONIC_DATA_ENCRYPTION_KEY.

TONIC_DATA_DECRYPTION_KEY and TONIC_DATA_ENCRYPTION_KEY can now be configured from the Environment Settings tab on Structural Settings .

Bug fixes and other internal updates.

MySQL - Fixed an issue with output to a container repository caused by a broken dependency update chain (kubernetes-client → YamlDotNet).

On the job details page, the Reports and Logs dropdown list now includes a View Gantt option, which allows you to view where time was spent during job execution. The option is only available for data generation jobs that used the Data Pipeline V2 process.