The following limitations apply to AutoML.
AutoML only supports datasets in the English language.
MySQL HeatWave AutoML does not support
TEXTcolumns withNULLvalues.MySQL HeatWave AutoML does not support target columns (a column with ground truth values) with a
TEXTdata type.MySQL HeatWave AutoML does not support recommendation tasks with columns that have a
TEXTdata type.For the forecasting task,
endogenous_variablescannot be inTEXT.
The
ML_TRAINroutine does not support MySQL user names that contain a period. For example, a user named'joe.smith'@'cannot run the%'ML_TRAINroutine. The model catalog schema created by theML_TRAINprocedure incorporates the user name in the schema name (for example.,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.
-
ML_EXPLAIN_TABLEandML_PREDICT_TABLEare compute intensive processes, withML_EXPLAIN_TABLEbeing 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 thebatch_sizeoption. See the following to learn more: ML_EXPLAIN,ML_EXPLAIN_ROW, andML_EXPLAIN_TABLEroutines limit explanations to the 100 most relevant features.The
ML_PREDICT_TABLEml_resultscolumn contains the prediction results and the data. This combination must be less than 65,532 characters.Concurrent MySQL AI analytics and AutoML queries are not supported. An AutoML query must wait for MySQL AI analytics queries to finish, and vice versa. MySQL AI analytics queries are given priority over AutoML queries.
The
ML_PREDICT_ROW,ML_MODEL_IMPORT, andML_MODEL_EXPORTroutines are not supported with theTwoTowerrecommendation model.