MySQL HeatWave AutoML has increased the maximum model size from 900MB. The MySQL HeatWave cluster shape you set for a DB system now defines the total memory available to train a model and for all loaded models. For imported models, we recommend individual models have a size of 4GB or less. (WL #15931)

MySQL HeatWave Autopilot includes improvements to cardinality estimation for queries that run in MySQL HeatWave and MySQL HeatWave Lakehouse. This improves the query plan, and provides improved performance (WL #15995)

MySQL HeatWave Autopilot now includes Auto Indexing Advisor that offers indexing suggestions to improve the performance and latency of OLTP workloads running on the MySQL HeatWave primary engine. (WL #15663)

MySQL HeatWave GenAI introduces similarity search capabilities that support the DISTANCE function that measures the distance between two vector values. It can include an optional distance_metric that can have a value of DOT, COSINE or EUCLIDIAN. This is available in the primary and secondary engines. (WL #16081)

MySQL HeatWave GenAI introduces the new native VECTOR data type and in-database vector store support. This provides a fast, end-to-end, fully integrated pipeline which automates the vector store creation:

(WL #16106)

MySQL HeatWave GenAI introduces a set of intuitive chat functionalities that enable enterprises to quickly build their own AI powered chatbot. It also introduces an out-of-the-box chatbot – MySQL HeatWave Chat, which integrates the chat functionalities that enable users to interact with MySQL HeatWave using natural language in addition to SQL. (WL #16248)

MySQL HeatWave GenAI introduces in-database LLM with support for the following LLMs, see Perform AI-Powered Search and Content Generation:

(WL #15844, WL #16145)

MySQL HeatWave Lakehouse now supports unstructured documents, and loads them to the GenAI vector store. Supported formats include PDF, HTML, TXT, PPT and DOCX. (WL #16100)

MySQL HeatWave Lakehouse introduces Lakehouse Incremental Load that uses change propagation to refresh data views following changes to a loaded table. (WL #15817)

MySQL HeatWave includes improvements to query optimization that lead to better performance for low latency queries in MySQL HeatWave and MySQL HeatWave Lakehouse. (WL #16222)

MySQL HeatWave includes improvements to change propagation performance. (WL #16148)

MySQL HeatWave improves the debugging of offloaded queries. (WL #15988)

MySQL HeatWave now supports the use of cursors from stored procedures. (WL #16142)

MySQL HeatWave now has support for the JSON data type with the following functions:

(WL #16048)

MySQL HeatWave now supports the following JSON functions:

(WL #16046, WL #16047)

MySQL HeatWave now includes support for GROUP_CONCAT() with DISTINCT optimization and the ORDER BY clause. (WL #15906)

MySQL HeatWave now supports dynamic query offload which uses machine learning based on query properties to determine the best engine, InnoDB or MySQL HeatWave analytic engine, to process the query. (WL #15829)

MySQL HeatWave now supports concurrent query execution that reduces query latencies, and increases resource utilization. (WL #14826)

MySQL InnoDB on MySQL HeatWave includes a bulk load extension to the LOAD DATA statement. This now uses multiple threads to load a series of CSV files to improve performance, and allow the LOAD operation to scale with multiple CPUs. (WL #15611)

MySQL InnoDB on MySQL HeatWave includes a bulk load extension to the LOAD DATA statement. This now supports large objects with VARCHAR and VARBINARY. It also supports the following data types:

See: Bulk Ingest Data. (WL #16264, WL #16265)