MySQL HeatWave Release Notes
These release notes were created with the assistance of MySQL HeatWave GenAI.
MySQL 9.3.0 onwards, to help you generate better quality
embeddings, MySQL HeatWave GenAI will use
multilingual-e5-small as the default
embedding model for encoding documents in all supported
languages including English. This means that
minilm will not be used as the default
embedding model for encoding English documents.
This default value change will impact the following processes:
New vector store tables will be created using
multilingual-e5-small by default.
Retrieval augmented generation (RAG) will search tables
created using the default embedding model,
multilingual-e5-small, unless you
explicitly specify the embedding model to use.
MySQL HeatWave AutoML now supports log anomaly detection, a new task that enables you to identify unusual patterns in log data. This feature is designed to help you detect and investigate potential issues more efficiently.
For more information, see Anomaly Detection for Logs. (WL #16579)
A new table state,
RECOVERYFAILED_RPDGSTABSTATE, has been
introduced for Lakehouse tables. During a MySQL HeatWave Cluster restart,
if a Lakehouse table cannot be recovered, its state is set to
RECOVERYFAILED_RPDGSTABSTATE to indicate that
it could not be recovered. The cluster remains usable even if
recovery of Lakehouse tables fail. Tables in the
RECOVERYFAILED_RPDGSTABSTATE state cannot be
used for queries or change propagation. You must reload tables
in this state by running SECONDARY_UNLOAD
followed by SECONDARY_LOAD, which lets you
identify errors and take corrective action.
For more information, see The rpd_tables Table. (WL #16626)
Lakehouse now supports detailed warnings summary for load and inference operations. The summary is included in the warning messages, providing an accurate list of warning codes and their respective counts. This enhancement helps you better understand and manage warnings encountered during Lakehouse operations.
For more information, see MySQL HeatWave Lakehouse Error Messages. (WL #16637)
MySQL HeatWave now supports columns wider than 64 KB, with a new maximum limit of 4 MB.
For more information, see Column Limits. (WL #16289)