New features (MySQL)

Release 4.7.0

This plugin release supports the following feature/features:

• Certification of RHEL 8.9

  • Certified MySQL and Percona v8.0 on RHEL v8.9 and lower.

Release 4.6.0

This plugin release supports the following feature/features:

• Certification of Amazon Linux 2

  • The Amazon Linux 2 operating system is certified against the MySQL connector and MySQL 8.0.X.

  • This ensures that when Amazon Linux 2 is the source environment (MySQL 8.0.X) and Amazon Linux 2 (MySQL 8.0.X) is the staging environment, staging push and replication flows work as expected. Finally, VDBs can be provisioned onto Amazon Linux 2 target environments.

• Certification of MySQL RDS / MySQL RDS Aurora with Amazon Linux 2 (Staging Push) - Staging Push is certified with AWS RDS and AWS RDS Aurora in AWS (PaaS) as a source and Amazon Linux 2 as a staging environment. 

• Custom backup folder for Delphix Initiated backup - By default, the /tmp folder was used to store the backup files during the Delphix initiated backup. With this release, customers can provide their backup folder with proper privileges. 

• Source Config parameters are now optional - While creating dSources with Staging Push, the installation (or Source Config) parameters are optional. However, they are required for the two replication-based linking mechanisms.

Release 4.5.0

This plugin release supports the following feature/features:

• Dynamic UI: This release introduces dynamic UI changes that will make only those fields visible that are required for the selected ingestion mechanism (dSource Type) staging push or replication. As part of this feature, the following changes have been made:

  • The Database List and Logsync fields are now removed from the linking screen.

  • Provide different Replication User is added on the linking screen. This field is used in scenarios where you explicitly want to provide different replication user credentials.

Release 4.4.0

This plugin release consists of only bug fixes.

Release 4.3.0

This release renames the ‘Manual Backup Ingestion’ mechanism to 'Staging Push’. You can notice this change when you create a dsource. For more information, refer to Linking using Staging Push mode.

Release 4.2.0

This connector version introduces data source sizing which enables users to calculate the size of ingested MySQL databases. For more information, refer to Source sizing implementation for MySQL dSources.

Release 4.1.0

This connector version blocks the creation, rollback, and refresh actions of VDBs on target environments when the installed MySQL version is not the same as the dSource’s installed MySQL version. This is a protective feature that prevents the accidental corruption of MySQL VDBs.

Release 4.0.0

This connector version supports MySQL v8 across all certified editions.

Release 3.0.0

This connector version has the following new features:

• The MySQL connector version 3.0.0 has been enhanced for improved security and stability. We have added fixes for the following:

  • Dataset creation workflows can detect if the provided port number is already in use by an existing MySQL instance and notify the user.

  • Corrected the reported dSource and VDB statuses.

  • Fixed the Snapshot with Parameters functionality of the Manual Backup Ingestion to work smoothly and without errors.

  • Improved UI descriptions, UI and connector validations, and error messages.

• Added support for Percona Server for MySQL version 5.7 using Manual Backup Ingestion and Binary Log Replication ingestion models.

• Integrated support for MySQL and Percona Server for MySQL version 5.7 in a consolidated release stream. If you have installed divergent or custom branches of the MySQL connector you should look to migrate to this production stream. Future features and bugs will be resolved here.

• Implemented various security fixes.

Release 2.1.0

The MySQL connector 2.1.0 release consists of security improvements.

Release 2.0.26

This connector version has the following new features:

• Selecting Databases: Ability to select specific databases in the Source MySQL server when creating a dSource.

• Delphix generated config file: If a my.cnf file is not provided while creating a dSource, Delphix now creates one.

• New Exit Return Codes: MySQL connector 2.0.26 introduces more granular error exit codes.

Delphix began supporting MySQL connector version from v2.0.26.