Fixed an issue where users could only select generators that supported uniqueness constraints for columns that were not unique.
Fixed an issue where admin users who did not have edit permissions on any workspaces could not edit presets from the Generator Presets view.
Improved data generation resiliency against transient failures.
Removed erroneous error messages.
To add AWS credentials to containers, you can now mount to ~/.aws/credentials.
Improved error messaging for Table View.
Fixed a display issue where the column configuration panel was too narrow and required horizontal scrolling.
Exporting or copying a workspace no longer requires the workspace to have a valid source database connection.
Reduced the amount of memory needed to run the Tonic web server.
MongoDB
- Better handling of errors that involve invalid UUIDs.
Oracle
- Updated the required permissions for destination database connections. If
SELECT ANY DICTIONARYorSELECT_CATALOG_ROLEcannot be granted, then Tonic can use a selection ofALL_views (not recommended). - If
TONIC_ORACLE_SKIP_CREATE_DB=true, then external tables are now excluded from the table list in Tonic. Tonic does not process those tables.
PostgreSQL
- Fixed an issue where the Data Pipeline V2 flow would hang.
- Fixed an issue where extensions such as pgcrypto were not transferred when data generation included schema filtering.
- Improved performance when handling constraints.
Snowflake on AWS
- As of V823, you can choose whether to use the Lambda process for data generation, which was previously the only option. By default, Snowflake on AWS uses a new, more resilient data generation process. You only need to use the Lambda data generation process for extremely large volumes of data (hundreds of gigabytes to terabytes).
For existing workspaces, for versions before V826, the new default process is used. To use the Lambda data generation process, you must update your workspace configuration. As of V826, existing workspaces use the Lambda data generation process. - For the temporary CSV files used to retrieve and write source and destination data, you can now specify to use an external stage instead of an S3 bucket. The option to use an external stage is not available when you use the Lambda data generation process.
- You can now specify different file storage locations for the temporary source and destination data files. In other words, you can have different S3 buckets or different external stages. Note that this option is not available when you use the Lambda data generation process.
- For the new data generation process, fixed an issue where data generation jobs would hang instead of failing.
Snowflake on Azure
- Before it runs a data generation, Tonic now verifies that there is a valid value for the Azure Blob Storage account key, which is set as the value of the environment variable
TONIC_AZURE_BLOB_STORAGE_ACCOUNT_KEY. - Fixed an issue where data generation jobs would hang instead of failing.
