To identify tables on the MySQL DB System that are defined
with a secondary engine, query the
CREATE_OPTIONS
column of the
INFORMATION_SCHEMA.TABLES
table. The CREATE_OPTIONS
column shows the
SECONDARY_ENGINE
clause, if defined. Tables
with SECONDARY_ENGINE="RAPID"
are loaded
into HeatWave, and changes to them are automatically propagated
to their counterpart tables in the HeatWave Cluster.
mysql> SELECT TABLE_SCHEMA, TABLE_NAME, CREATE_OPTIONS
FROM INFORMATION_SCHEMA.TABLES
WHERE CREATE_OPTIONS LIKE '%SECONDARY_ENGINE%' AND TABLE_SCHEMA LIKE 'tpch';
+--------------+------------+--------------------------+
| TABLE_SCHEMA | TABLE_NAME | CREATE_OPTIONS |
+--------------+------------+--------------------------+
| tpch | customer | SECONDARY_ENGINE="RAPID" |
| tpch | lineitem | SECONDARY_ENGINE="RAPID" |
| tpch | nation | SECONDARY_ENGINE="RAPID" |
| tpch | orders | SECONDARY_ENGINE="RAPID" |
| tpch | part | SECONDARY_ENGINE="RAPID" |
| tpch | partsupp | SECONDARY_ENGINE="RAPID" |
| tpch | region | SECONDARY_ENGINE="RAPID" |
| tpch | supplier | SECONDARY_ENGINE="RAPID" |
+--------------+------------+--------------------------+
You can also view create options for an individual table using
SHOW CREATE TABLE
.
Before MySQL 8.0.31, it may be necessary to exclude the
SECONDARY ENGINE
option from
CREATE TABLE
statements when
creating a dump file, as DDL operations cannot be performed
on tables defined with a secondary engine in those releases.
You can use the
show_create_table_skip_secondary_engine
variable to exclude the SECONDARY ENGINE
clause from SHOW CREATE
TABLE
output, and from CREATE
TABLE
statements dumped by the
mysqldump utility.
mysqldump also provides a
--show-create-skip-secondary-engine
option that enables the
show_create_table_skip_secondary_engine
system variable for the duration of the dump operation.