The following limitations apply to AutoML.
AutoML only supports datasets in the English language.
MySQL HeatWave AutoML does not support
TEXT
columns withNULL
values.MySQL HeatWave AutoML does not support target columns (a column with ground truth values) with a
TEXT
data type.MySQL HeatWave AutoML does not support recommendation tasks with columns that have a
TEXT
data type.For the forecasting task,
endogenous_variables
cannot be inTEXT
.
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 theML_TRAIN
procedure 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_TABLE
andML_PREDICT_TABLE
are compute intensive processes, withML_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 thebatch_size
option. See the following to learn more: ML_EXPLAIN
,ML_EXPLAIN_ROW
, andML_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 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.