When an InnoDB table is loaded into MySQL HeatWave Cluster, DDL operations such as ALTER TABLE, RENAME TABLE, TRUNCATE TABLE, and DROP TABLE are permitted. While any of these operations are being executed, queries involving the modified table are not offloaded to the MySQL HeatWave engine; they are processed by InnoDB. If you are explicitly trying to use the secondary engine, these queries generate an offload error.

It is recommended that you avoid expensive queries on a table immediately after performing a DDL operation.

Reload the table into the secondary engine. Queries accessing the table cannot be offloaded until the reload is complete.

To check the status and the progress of the tables present in MySQL HeatWave, run the following query:

mysql> SELECT SCHEMA_NAME, TABLE_NAME, LOAD_STATUS, LOAD_PROGRESS, LOAD_TYPE 
  FROM performance_schema.rpd_tables NATURAL JOIN performance_schema.rpd_table_id;
+-------------+-------------------+---------------------+---------------+-----------+
| SCHEMA_NAME | TABLE_NAME        | LOAD_STATUS         | LOAD_PROGRESS | LOAD_TYPE |
+-------------+-------------------+---------------------+---------------+-----------+
| airportdb   | flight_temp       | AVAIL_RPDGSTABSTATE |           100 | USER      |
| airportdb   | passengerdetails  | AVAIL_RPDGSTABSTATE |           100 | USER      |
| airportdb   | airport           | AVAIL_RPDGSTABSTATE |           100 | USER      |
+-----------------------------------------------------------------------------------+

The following DDL statements do not initiate a data reload in MySQL HeatWave: