Tonic Structural release information

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

File connector - Fixed an issue where, when a file column contained special characters, Table View did not load the columns correctly.

MongoDB - Fixed an issue that prevented Collection View from loading because of stuck scan jobs.

For certain specific column types, the Constant Generator could suggest invalid values, this issue has been fixed.

File connector: Added a new configuration setting TONIC_FILE_READ_PARALLELISM to enable parallel processing of multiple files. The setting is override-able within the workspace Advanced Workspace Overrides.

Fixed an issue where when a workspace was transferred to a new owner, and the original creator was deleted, the connection data became inaccessible.

During upsert, to accommodate schema changes in the destination database, we can now automatically add columns, whether those columns are nullable or not nullable, and whether or not the columns have default values.

Fixed a regression introduced in v1481 where database configurations that used SSH tunnels caused data generation to fail.

For Structural Cloud, on Structural Settings view, the Okta sign-in redirect URL is now displayed on the Single Sign-On tab under Access Management. You can then copy the value from there and paste it into Okta.

Oracle - A new environment setting, TONIC_ORACLE_SKIP_DESTINATION_PRIVILEGE_CHECK, allows bypassing the destination database privilege check when TONIC_ORACLE_SKIP_CREATE_DB is also set to true.

SQL Server - Limited the scope of editions for which online index creation is applied.

File connector - Fixed a regression in v1473 where users could not download generated files from a local files workspace.

Additional HTTP security headers added to Structural Cloud environment.

Structural now allows greater control over the number of documents fetched for Document View columns and document-based databases.

A new optional setting, CONTAINERIZATION_POD_SERVICEACCOUNT_NAME, sets the spec.serviceaccountName on datapacker pods.

Managing Ephemeral output from Structural - For workspaces that write output to Tonic Ephemeral, a new Outputs tab provides access to the Ephemeral snapshots and databases that were created from the workspace.

During upsert, to accommodate schema changes in the destination database, we can now rename columns that do not have constraints and delete columns.

Tonic Structural telemetry no longer includes the following information:

• IP address

• City

• Country

• Region

• Designated market area

• Carrier

• Device manufacturer

• Device model

Improved the Structural OpenAPI document to correctly indicate whether properties are nullable in request and response models. This change does not introduce any functional changes to the API behavior.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Fixed an issue that blocked logins using Duo SSO.

Fixed an issue that caused sensitivity scans to fail on workspaces that contained document columns and where Tonic Table Parallelism was set to 2 or above.

On the workspace settings page, replaced the Block Data Generation on Schema Changes toggle with a set of options. The new options are Do Not Block, Block On Sensitive Changes, and Block On All Changes.

SQL Server - Added logic to replace double quotes around the constant expression portion of Default object creation scripts with single quotes.

Structural now correctly preserves the original value for columns that contain constant values and that are assigned the Continuous generator. A previous fix addressed this partially, but some edge cases still caused the original value to be lost or triggered an error during generation. This is now fully resolved.

SQL Server - Fixed a performance regression when masking tables that have large row volumes.

Fixed a regression in v1464 that caused periodic schema change checks to not operate as expected.

MySQL - The classic data generation process is no longer available. All data generation for MySQL uses the Data Pipeline V2 process.