MySQL HeatWave AutoML only supports datasets in the English language.

MySQL HeatWave AutoML does not support text columns with NULL values.

MySQL HeatWave AutoML does not support a text target column.

MySQL HeatWave AutoML does not support recommendation tasks with a text column.

For the forecasting task, endogenous_variables cannot be text.

The ML_TRAIN routine does not support MySQL user names that contain a period. For example, a user named 'joe.smith'@'%' cannot run the ML_TRAIN routine. The model catalog schema created by the ML_TRAIN procedure incorporates the user name in the schema name (e.g., ML_SCHEMA_joesmith), and a period is not a permitted schema name character.

The table used to train a model cannot exceed 10 GB, 100 million rows, or 1017 columns.

As of MySQL 9.0.0, the shape you set for the MySQL HeatWave cluster in the DB system 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. ML_TRAIN will fail to run and raises an error if it attempts to train a model larger than this. Before MySQL 9.0.0, the limit was 900 MB. To query all loaded models and relevant model sizes, see ML_MODEL_ACTIVE

MySQL HeatWave on AWS only supports MySQL HeatWave AutoML with the MySQL HeatWave.256GB node shape. To use MySQL HeatWave machine learning functionality, select that shape when creating a MySQL HeatWave Cluster.

ML_EXPLAIN_TABLE and ML_PREDICT_TABLE are compute intensive processes, with ML_EXPLAIN_TABLE being the most compute intensive. Limiting operations to batches of 10 to 100 rows by splitting large tables into smaller tables is recommended. Use batch processing with the batch_size option. See the following to learn more:

ML_EXPLAIN, ML_EXPLAIN_ROW, and ML_EXPLAIN_TABLE routines limit explanations to the 100 most relevant features.

The ML_PREDICT_TABLE ml_results column contains the prediction results and the data. This combination must be less than 65,532 characters.

Concurrent MySQL HeatWave analytics and MySQL HeatWave AutoML queries are not supported. A MySQL HeatWave AutoML query must wait for MySQL HeatWave analytics queries to finish, and vice versa. MySQL HeatWave analytics queries are given priority over MySQL HeatWave AutoML queries.