HeatWave User Guide  /  ...  /  Lakehouse Limitations for all File Formats

5.8.1 Lakehouse Limitations for all File Formats

  • See Section 2.18.9, “Other Limitations” for all HeatWave MySQL query related limitations.

  • Do not create Lakehouse tables on the source DB in a replicated MySQL DB System if any of the replicas are outside HeatWave on OCI or HeatWave on AWS. This will cause replication errors.

  • Before MySQL 8.4.0-u2, a replication channel might fail if a HeatWave Cluster is added to a replica of a MySQL DB System, and later manually stopped.

  • It is not possible to dump external tables using the MySQL Shell export utilities, such as dumpInstance(). External tables are not replicated to InnoDB storage and cannot be exported. To export InnoDB data from a Lakehouse enabled database, exclude the external tables with an excludeTables option.

  • It is not possible to restore a backup from a Lakehouse enabled MySQL DB System to a standalone MySQL DB System.

  • A Lakehouse enabled MySQL DB System can support a maximum of 512 nodes.

  • Before MySQL 8.4.0, Lakehouse does not enforce any specified constraints. For example, Lakehouse does not enforce primary key uniqueness constraints. MySQL 8.4.0 removes this limitation.

  • Before MySQL 9.0.1-u1, the limit for the Lakehouse error message count is 100. As of MySQL 9.0.1-u1, Lakehouse supports max_error_count.

  • The lakehouse_filter_warning_codes_list session variable has a limit of 50 codes and 250 characters.

  • HeatWave Lakehouse does not support the following: