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.
You can now override the following environment settings in individual workspaces:
TONIC_READ_RANGES_PARALLELISMTONIC_PARTITION_PARALLELISMTONIC_FILE_GROUP_PARALLELISMTONIC_BIGQUERY_READ_PARALLELISMTONIC_ORACLE_DATA_PUMP_PARALLELISMTONIC_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.
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 .
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.
For the Conditional generator, fixed an issue where when a condition was based on other columns, the generator preview was not correct.
MySQL: Structural now restores preserved tables and triggers in the event of a failure.
SQL Server - Fixed a bug where history table settings and indexes were not appropriately replicated in the destination database.
Webhooks - new GitHub Actions webhook type - You can now configure a webhook that runs a GitHub action when the webhook is triggered. You specify the GitHub repository and credentials, and select the workflow. Structural then prompts you to provide the input values. The original type of webhook is now referred to as a custom webhook.
Webhooks - new schema change trigger type - You can now trigger a webhook when Structural detects a schema change. Previously, you could only trigger webhooks based on a job status.
Fixed an issue where nullable boolean environment settings were saved as null but could not be edited in the application.
Fixed an issue where nullable integer settings with default values could not be set to null when adding or editing.
MySQL - When a workspace writes output to a container repository, if the sql_mode cannot be determined from the source database - either from the SESSION or GLOBAL config - instead of leaving sql_mode unset, data packer now falls back to a sensible default value.
MySQL, Oracle: When calculating the percentage for subsetting target tables, Structural now uses the correct row counts.
Fixed an issue with unexpected behavior when the environment setting TONIC_STATISTICS_SEED is not set.
Updated the styling for Schema Changes view.
On Schema Changes view, added a button to display filtered tDatabase Viewo display all of the schema change columns.
Created a new generator for the Finnish Personal Identity Code.
You must specify a date range, and the generator will validate whether the input data falls within that period and if they are valid identity codes.
After that, a new Finnish Personal Identity Code will be generated so that the new birth date is within the selected range. A random valid century indicator will also be chosen, as well as a sequential number between 002 and 899.
Finally, the check digit will be calculated.
The new generator supports data consistency.
