Related Documentation Download this Manual
PDF (US Ltr) - 0.6Mb
PDF (A4) - 0.6Mb


HeatWave User Guide  /  Loading Data  /  Change Propagation

4.2 Change Propagation

After tables are loaded into HeatWave, data changes are automatically propagated from InnoDB tables on the MySQL DB System to their counterpart tables in the HeatWave cluster.

Changes accumulate on the MySQL DB System node and are propagated to HeatWave in batch transactions. Change propagation occurs every 200 milliseconds or when pending changes reach 64 MBs in size. Changes are applied using the READ COMMITTED isolation level.

A change propagation failure can cause table data in HeatWaveto become stale. Queries that access stale table data are not offloaded to HeatWave for processing. To check if change propagation is enabled globally, query the rapid_change_propagation_status variable:

mysql> SELECT VARIABLE_VALUE FROM performance_schema.global_status 
       WHERE VARIABLE_NAME = 'rapid_change_propagation_status';
+----------------+
| VARIABLE_VALUE |
+----------------+
| ON             |
+----------------+

To check if change propagation is enabled for individual tables, query the POOL_TYPE data in HeatWave Performance Schema tables. RAPID_LOAD_POOL_TRANSACTIONAL indicates that change propagation is enabled for the table. RAPID_LOAD_POOL_SNAPSHOT indicates that change propagation is disabled.

mysql> SELECT NAME, POOL_TYPE FROM rpd_tables,rpd_table_id 
       WHERE rpd_tables.ID = rpd_table_id.ID AND SCHEMA_NAME LIKE 'tpch';
+---------------+-------------------------------+
| NAME          | POOL_TYPE                     |
+---------------+-------------------------------+
| tpch.orders   | RAPID_LOAD_POOL_TRANSACTIONAL |
| tpch.region   | RAPID_LOAD_POOL_TRANSACTIONAL |
| tpch.lineitem | RAPID_LOAD_POOL_TRANSACTIONAL |
| tpch.supplier | RAPID_LOAD_POOL_TRANSACTIONAL |
| tpch.partsupp | RAPID_LOAD_POOL_TRANSACTIONAL |
| tpch.part     | RAPID_LOAD_POOL_TRANSACTIONAL |
| tpch.customer | RAPID_LOAD_POOL_TRANSACTIONAL |
+---------------+-------------------------------+

If change propagation is disabled for a particular table, you must unload and reload the table. See Chapter 5, Unloading Tables, and Chapter 4, Loading Data.

Change propagation does not support cascading changes triggered by a foreign key constraint.

Change propagation is aborted if dictionary-encoded string column updates cause a dictionary overflow, which occurs if the number of new unique values exceeds dictionary capacity.