MySQL HeatWave on AWS  /  Release Notes

19 Release Notes

Release notes for MySQL HeatWave on AWS

2024-04-08, General Availability

You can now explore MySQL HeatWave on AWS features using sample databases. See Importing Sample Database for details.

2024-03-04, General Availability

  • Events allow you to monitor the state changes of resources such as DB Systems, HeatWave Clusters, and Backups. An event reports a create, update, or delete operation for a resource, or its lifecycle state change. Events are listed under the Events tab of the corresponding resource. For more details, see Events.

2024-02-20, General Availability

2024-02-15, General Availability

  • MySQL HeatWave on AWS now supports the MySQL Enterprise Audit plugin. The audit plugin enables the MySQL Server to produce a log file containing an audit record of server activities such as when clients connected and disconnected, what actions they performed while being connected, and which databases and tables they accessed. You can also add statistics for the time and size of the queries performed. See MySQL Enterprise Audit for details.
  • You can now create a custom configuration by copying an existing MySQL configuration and modifying its user variables. You can then apply the custom configuration to a DB System. For more information, see Copying a MySQL Configuration and Update MySQL Configuration.

2024-01-24, General Availability

  • MySQL HeatWave on AWS now supports MySQL version 8.3.0.

2024-01-17, General Availability

  • MySQL HeatWave on AWS supports inbound replication that does not use GTID auto-positioning, and also for tables that do not have primary keys. See Creating a Channel for details.

2023-12-21, General Availability

  • The Auto Shape Prediction feature in MySQL Autopilot has been enhanced. In addition to the overall buffer pool usage, workload activity, and access patterns, Auto Shape Prediction now utilizes the CPU statistics to estimate the required buffer pool size and CPU cores. See Autopilot Shape Advisor for details.

2023-11-28, General Availability

  • MySQL HeatWave on AWS supports adding filters in inbound  replication. Filters allows you to selectively replicate databases and  tables from the MySQL source. For more information on inbound  replication filters, please see Channel Filter Rules for Inbound Replication.
  • MySQL HeatWave on AWS introduces delayed inbound replication.  You can choose to specify the time (in seconds) to wait before the  target DB System in MySQL HeatWave on AWS replicates the source  transactions. For more information on delayed replication, please see Replication delay.

2023-11-16, General Availability

  • MySQL HeatWave on AWS supports inbound replication from a MySQL source to a MySQL DB System.

    For more information on the inbound replication feature, see Inbound Replication.

  • You can now update a HeatWave Cluster's size and shape. For more information, see Editing a HeatWave Cluster.

2023-10-26, General Availability

  • MySQL HeatWave on AWS supports MySQL version 8.2.0.

2023-09-13, General Availability

  • MySQL HeatWave on AWS introduces a faster and easier feature to import data from an Amazon S3 bucket into a MySQL DB System. The data import feature enables you to import data in a variety of formats such as MySQL dump and text files (such as CSV and TSV).

    For more information on the data import feature, see Data Import Feature.

  • MySQL HeatWave on AWS supports the bulk ingest feature to import text files (such as CSV and TSV) directly from an Amazon S3 bucket into a MySQL DB System. This method is faster and more efficient in terms of computing and storage consumption. To use the bulk ingest feature, first connect to the DB system, and then import data in an existing or new table using the BULK algorithm.

    For more information on the bulk ingest feature, see Bulk Ingest Feature.

2023-08-08, General Availability

  • You can now increase the data storage size of an active DB System online. When the DB System is active and healthy, updating the data storage size of the DB System does not restart the DB System, and you can continue to query it while the storage is being increased. You get elasticity without compromising uptime or performance.

    For more information, see Increasing DB System Storage.

2023-07-31, General Availability

  • MySQL HeatWave on AWS now supports auto error recovery. Whenever a HeatWave node fails because of a hardware or a software issue, the cluster becomes unhealthy and error recovery is triggered. During the recovery process, HeatWave automatically attempts to bring the node online and reload data that was previously loaded. This reduces manual intervention and improves service uptime.

    For more information, see HeatWave Cluster Failure and Recovery.

2023-07-13, General Availability

  • MySQL HeatWave on AWS is now available in the AWS Europe (Frankfurt) and Europe (London) region. See Region Availability.
  • Fast data reload is now available when you pause and resume HeatWave on AWS. Besides storing the HeatWave formatted data in-memory, HeatWave also stores the formatted data in HeatWave storage layer on AWS S3. This enables reload of data in constant time regardless of data size. This capability is now available when you pause and resume the HeatWave cluster. You can now pause the HeatWave cluster when you don't need it to save cost, and resume the cluster very fast when you want to use HeatWave for query acceleration.

2023-06-08, General Availability

  • MySQL HeatWave on AWS is now available in the AWS Asia Pacific (Mumbai) region. See Region Availability.

2023-05-04, General Availability

  • MySQL HeatWave on AWS is now available in the AWS Asia Pacific (Tokyo) region. See Region Availability.

2023-04-27, General Availability

  • HeatWave Scale-out Data Management on AWS S3

    MySQL HeatWave on AWS now provides an optimized storage layer built on AWS S3 to store the HeatWave in-memory hybrid columnar representation of the data. This allows data to be reloaded to each HeatWave node independently and in parallel. This significantly improves the service uptime and performance of operations such as error recovery, maintenance, and system restart. See HeatWave Architectural Features.

  • MySQL Autopilot: Auto Error Recovery from MySQL failure

    With Auto Error Recovery, now when MySQL fails and restarts, the HeatWave Cluster automatically restarts, identifies the tables which were loaded prior to the failure, and reloads those tables automatically from MySQL. This reduces the intervention by the user and also improves service uptime.

  • Auto reload of data in HeatWave Cluster after MySQL upgrade

    HeatWave now automatically reloads data from MySQL InnoDB after a MySQL node restarts due to maintenance upgrades or planned restarts. With auto-reload capability, there are no more manual steps after maintenance or a restart operation. This reduces the operational overhead and improves service availability.

  • MySQL Autopilot for OLTP - Auto Shape Prediction

    Auto shape prediction collects the most recent query execution metrics and uses advanced machine learning models to predict the MySQL database instance shape for optimal transactional processing performance. Auto shape prediction continuously monitors OLTP workload to provide a suggestion that will adapt to evolving workload patterns, allowing the MySQL DB System to maintain the best OLTP price performance over time. See Autopilot Shape Advisor.

    Monitor MySQL statistics such as buffer pool usage, workload activity and access patterns, and recommendations for the optimal MySQL shape for the workload with MySQL HeatWave Console.

  • MySQL Configuration

    Use MySQL HeatWave Console to view and configure user, system, initialization, and service-specific variables for the MySQL DB System shape with or without HeatWave support. Select a default configuration or create a custom configuration for the DB system. See and Configuration.

  • Automatic Backup

    MySQL HeatWave on AWS now support automatic backups. Choose a time for automatic backups during the creation of a MySQL DB System. The retention period can be between 1 and 35 days. The default retention period is 7 days. Scheduled backups are deleted when the DB System is deleted. See Creating a DB System.


PREV   HOME   UP