3.2 HeatWave AutoML Prerequisites

As of MySQL 9.0.0, HeatWave AutoML can support large models that are only limited by the amount of memory defined by the shape.

• An operational MySQL DB System.

  • For HeatWave on OCI, see Creating a DB System in the HeatWave on OCI Service Guide.

  • For HeatWave on AWS, see Creating a DB System in the HeatWave on AWS Service Guide.

  • For HeatWave for Azure, see Provisioning HeatWave in the HeatWave for Azure Service Guide.

• An operational HeatWave Cluster.

  • For HeatWave on OCI, see Adding a HeatWave Cluster in the HeatWave on OCI Service Guide.

  • For HeatWave on AWS, see Creating a HeatWave Cluster in the HeatWave on AWS Service Guide.

  • For HeatWave for Azure, see Provisioning HeatWave Nodes in the HeatWave for Azure Service Guide.

• MySQL Shell 8.0.22 or higher.

  • For HeatWave on OCI, see Connecting to a DB System in the HeatWave on OCI Service Guide.

  • For HeatWave on AWS, see Connecting with MySQL Shell in the HeatWave on AWS Service Guide.

• The MySQL account that will train a model does not have a period character (".") in its name; for example, a user named 'joesmith'@'%' is permitted to train a model, but a user named 'joe.smith'@'%' is not. For more information about this requirement, see Section 3.19, “HeatWave AutoML Limitations”.

• The MySQL account that will use HeatWave AutoML has been granted the following privileges:

  • SELECT and ALTER privileges on the schema that contains the machine learning datasets; for example:

    mysql> GRANT SELECT, ALTER ON schema_name.* TO 'user_name'@'%';

  • SELECT and EXECUTE on the MySQL sys schema where HeatWave AutoML routines reside; for example:

    mysql> GRANT SELECT, EXECUTE ON sys.* TO 'user_name'@'%';