22 Release Notes

Release notes for HeatWave on AWS

2024-10-23: MySQL 9.1.0 Now Supported

HeatWave on AWS now supports MySQL 9.1.0, the latest Innovation Release of the MySQL Server. Innovation Release 9.1.0 includes new features and bug fixes. If you want to access the latest features and improvements and stay updated with the latest technologies, the MySQL Innovation Releases might be the best choice for you. You can choose release 9.1.0 when creating a new DB System, and for existing DB Systems, you can manually upgrade to MySQL 9.1.0. Refer to MySQL 9.1.0 Release Notes and Upgrade MySQL Version.

2024-10-16: Enhanced Console Navigation

The HeatWave on AWS Console has been enhanced with improved navigation. Page-level navigation is now relocated to a new collapsible sidebar and the Performance and HeatWave AutoML tabs are merged into the Workspace tab. See Console Overview for details.

2024-09-18: HeatWave Console Home Screen Enhanced

The console home screen now has a new Monitoring tab. The tab contains a new Service Events pane. See Console Overview for details.

2024-09-04: HeatWave GenAI Now Available

• HeatWave on AWS now supports HeatWave GenAI. It provides integrated and automated generative AI with in-database large language models (LLMs), an automated, in-database vector store, and the ability to have contextual conversations in natural language. HeatWave GenAI enables enterprises to use generative AI without AI expertise, data movement, or additional cost. See HeatWave GenAI for details.

2024-08-22: HeatWave Console Home Screen Refreshed

The HeatWave on AWS console now has a new home screen for an enhanced user experience. It has the following improvements:

• Revamped with key information presented in a dashboard-like layout. There is now a What's New pane, listing latest changes to the HeatWave Console.
• The HeatWave MySQL and HeatWave Clusters tabs are now consolidated into a new Resources tab. There is now a HeatWave Clusters tab on the new Resources page, for information and actions on the HeatWave Clusters.
• The Workspaces tab is renamed to Workspace.

2024-08-22: PrivateLink Now Supported for Inbound replication

• HeatWave on AWS now supports inbound replication on a PrivateLink. It enables secure data replication from an external system running in your AWS account to HeatWave on AWS. See Configuring Inbound Replication over an Egress PrivateLink for details.

2024-08-08: DB System Shapes Now Changeable

• You can now reduce the shape of a DB System to save cost or expand the shape to enhance the DB System's function or performance. Decisions on shape changes are aided by the Autopilot Shape Advisor, which uses the system workload to access the suitability of a shape and make recommendations on shape changes. See Update MySQL Shape for details.

2024-07-10: MySQL 9.0.0 Now Supported

• HeatWave on AWS now supports MySQL 9.0.0, the latest Innovation Release of the MySQL Server. Innovation Release 9.0.0 includes new features and bug fixes. If you want to access the latest features and improvements and stay updated with the latest technologies, the MySQL Innovation Releases might be the best choice for you. You can choose release 9.0.0 when creating a new DB System, and for existing DB Systems, you can manually upgrade to MySQL 9.0.0. Refer to MySQL 9.0.0 Release Notes and Upgrade MySQL Version.

2024-07-10: Autopilot Index Advisor Now Available

• You can now enhance the performance of OLTP workloads on DB Systems running MySQL Server 9.0.0 or later by utilizing the Autopilot Index Advisor, which provides recommendations for secondary indexes. See Autopilot Index Advisor for details.

2024-06-25: AWS PrivateLink Now Supported

• You can now utilize AWS PrivateLink to establish a secure connection to HeatWave on AWS from your VPC. This ensures that sensitive data such as customer details remain protected from the internet, enabling secure and private transfer of critical data in a scalable manner. For more information, please refer to PrivateLink.

2024-06-25: HeatWave Lakehouse Now Available

• HeatWave on AWS now includes HeatWave Lakehouse, enabling organizations to process and query hundreds of terabytes of data stored in object storage and optionally combine it with transactional data in MySQL databases without copying the data from the object storage into the MySQL database. Customers can also use this data loaded from the object storage to train machine learning models, run inferences, and explain results, without moving the data to a separate ML service. With Lakehouse, HeatWave on AWS offers a single service for analytics across data warehouses and data lakes, machine learning, and transaction processing, eliminating the need for ETL across cloud services. For more information, please refer to Creating Lakehouse Mapping.

2024-06-25: Free Trial for MySQL HeatWave on AWS Now Available

• You can now try out MySQL HeatWave on AWS for free without having to upgrade to a paid Oracle Cloud account. See Try MySQL HeatWave for free and Sign-up Overview for details.

2024-05-22: MySQL 8.4.0 Now Supported

• MySQL HeatWave on AWS now supports MySQL 8.4.0. See MySQL 8.4.0 Release Notes for more information on the server release.

  MySQL 8.4.0 marks the start of a new series of LTS (Long Term Support) releases. The 8.4 LTS releases will focus on security and bug fixes and are recommended for customers who prefer established behavior, while the next innovation series will include new features.

  We recommend customers who are using any lower versions of MySQL Server to upgrade to MySQL 8.4.0. See Upgrade MySQL Version for instructions.

2024-05-02: Pre-configured DB System Now Available

• You can now explore the capabilities of MySQL HeatWave on AWS by launching a pre-configured DB System with sample data. See Launching a Starter DB System for details.

2024-04-08: Sample Database Now Available

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

2024-03-04: Events Tab Added to the Console

• 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: Custom MySQL Configurations Can Now be Created

• 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-02-15: MySQL Enterprise Audit Now Supported

• 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.

2024-01-24: MySQL 8.3.0 Now Supported

• MySQL HeatWave on AWS now supports MySQL version 8.3.0.

2024-01-17: Inbound Replication Support Now Further Enhanced

• 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: Auto Shape Prediction Now Enhanced

• 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: Inbound Replication Support Now Enhanced

• 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: Inbound Replication Now Supported

• 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: MySQL 8.2.0 Now Supported

• MySQL HeatWave on AWS supports MySQL version 8.2.0.

2023-09-13: Improved Data Import Methods Now Supported

• 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: Data Storage Size Can Now Be Increased

• 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: Auto Error Recovery Now Supported

• 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: MySQL HeatWave on AWS Now Available in More Regions

• MySQL HeatWave on AWS is now available in the AWS Europe (Frankfurt) and Europe (London) region. See Region Availability.

2023-07-13: Fast Data Reload Now Available

• 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: MySQL HeatWave on AWS Now Available in the AWS Asia Pacific (Mumbai) Region

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

2023-05-04: MySQL HeatWave on AWS Now Available in the AWS Asia Pacific (Tokyo) Region

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

2023-04-27: New Features Now 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.