From the Confirm Generation panel, the option to upload job logs to Tonic.ai is now available even if diagnostic logging is not enabled.
File connector - As a safety precaution, data generation for Amazon S3 or GCS workspaces do not process any input files for which the output path points to itself, which could happen in rare output path configurations. Previously, any files in the output location were overwritten.
On the workspace settings and Schema Changes view, “sensitive schema changes” are now referred to as “schema changes that could expose data”. This is to avoid confusion with the general sensitivity designation for columns.
File connector - On the Workspace Settings page, added support for testing credentials and configurations.
Files connector - For Amazon S3 or GCS workspaces, fixed a regression that prevented users without permission to list all buckets from being able to load the workspace properly.
Fixed an issue where a new deployment could cause the application to fail during navigation.
Added a Format Type configuration option when the Timestamp Shift generator is assigned to numeric columns.
For jobs that generate diagnostic logs, the job details page now includes an option to send the logs directly to Tonic.ai.
Snowflake - Fixed an issue where subsetting data generation failed when primary or foreign key columns had names that conflicted with particular SQL keywords.
File connector - Fixed an issue that caused invalid modifications to file groups.
When a workspace is configured to not block data generation when there are schema changes, then before a data generation can run, there must be a completed schema diff.
MySQL - You can now exclude specific views from data generation. To identify the views to exclude, use the environment setting TONIC_MYSQL_EXCLUDED_TABLES_FROM_DUMP. The value is a comma-separated list of tables and views to exclude.
In Document View, fixed an issue where fields in sparse documents could be dropped from Hybrid view when the Preview option was toggled on.
