HeatWave Release Notes
When a MySQL HeatWave Cluster is enabled, queries that meet certain prerequisites are automatically offloaded from the DB System to the MySQL HeatWave Cluster for accelerated processing.
Queries are issued from a MySQL client or application that interacts with the MySQL HeatWave Cluster by connecting to the DB System. Results are returned to the DB System and to the MySQL client or application that issued the query.
Manually loading data into MySQL HeatWave involves preparing tables on the DB System and executing load statements. The Auto Parallel Load utility facilitates the process of loading data by automating required steps and optimizing the number of parallel load threads. See Section 4.2.5, “Load Data Using Auto Parallel Load”.
For MySQL HeatWave on AWS, load data into MySQL HeatWave using the MySQL HeatWave Console. See Manage Data in MySQL HeatWave with Workspaces in the MySQL HeatWave on AWS Service Guide.
For MySQL HeatWave for Azure, see Importing Data to MySQL HeatWave in the MySQL HeatWave for Azure Service Guide.
When MySQL HeatWave loads a table, the data is sharded and distributed among MySQL HeatWave nodes. After a table is loaded, DML operations on the tables are automatically propagated to the MySQL HeatWave nodes. No user action is required to synchronize data. For more information, see Section 4.2.7, “About Change Propagation”.
Data loaded into MySQL HeatWave, including propagated changes, automatically get persisted in the MySQL HeatWave Storage Layer to Object Storage for fast recovery in case of a MySQL HeatWave node or cluster failure.
As of MySQL 9.2.0, MySQL HeatWave Storage Layer persists additional metadata to allow fast recovery after a planned or unplanned restart of Standalone DB system (without High Availability). This enables MySQL HeatWave to reload data from the Storage Layer after the DB System restarts. In previous versions of MySQL, MySQL HeatWave reloads data from the original source, InnoDB or the Object Storage in case of Lakehouse tables, which takes longer for data to reload.
After running a number of queries, use the MySQL HeatWave Autopilot Advisor to optimize the workload. Advisor analyzes the data and query history to provide string column encoding and data placement recommendations. See Section 5.8, “Optimize Workloads for OLAP”.
Check the list of supported data types, supported SQL modes, and supported functions and operators.