bulk_loader.data_memory_size

Specifies the amount of memory to use for LOAD DATA with ALGORITHM=BULK, in bytes. See: Section 4.1.2, “Bulk Ingest Data”.

bulk_loader.concurrency

The maximum number of concurrent threads to use by one LOAD statement with ALGORITHM=BULK. See: Section 4.1.2, “Bulk Ingest Data”.

bulk_loader.chunk_size

The queue chunk size in MiB used for reading data from CSV files.

lakehouse_filter_warning_codes_list

Specifies the warning codes for Lakehouse to filter.

lakehouse_filter_warning_modes_list

Specifies the warning modes for Lakehouse to filter.

rapid_compression

Whether to enable or disable data compression before loading data into MySQL HeatWave. Data compression is enabled by default. The setting does not affect data that is already loaded. See Section 4.2.3, “Enable or Disable Data Compression”.

The default option is AUTO which automatically chooses the best compression algorithm for each column.

rapid_bootstrap

The setting for this variable is managed by OCI and cannot be modified directly. Defines the MySQL HeatWave Cluster bootstrap state. States include:

rapid_dmem_size

The setting for this variable is managed by OCI and cannot be modified directly. Specifies the amount of DMEM available on each core of each node, in bytes.

rapid_memory_heap_size

The setting for this variable is managed by OCI and cannot be modified directly. Defines the amount of memory available for the MySQL HeatWave plugin, in bytes. Ensures that MySQL HeatWave does not use more memory than is allocated to it.

rapid_execution_strategy

Specifies the query execution strategy to use. Minimum runtime (MIN_RUNTIME) or minimum memory consumption (MIN_MEM_CONSUMPTION).

MySQL HeatWave optimizes for network usage rather than memory. If you encounter out of memory errors when running a query, try running the query with the MIN_MEM_CONSUMPTION strategy by setting by setting rapid_execution_strategy prior to executing the query:

SET SESSION rapid_execution_strategy = MIN_MEM_CONSUMPTION;

See Section 11.1.1, “MySQL HeatWave Issues”.

rapid_stats_cache_max_entries

The setting for this variable is managed by OCI and cannot be modified directly. Specifies the maximum number of entries in the statistics cache.

The number of entries permitted in the statistics cache by default is 65536, which is enough to store statistics for 4000 to 5000 unique queries of medium complexity.

For more information, see Section 5.4.12, “Auto Query Plan Improvement”.

rapid_ml_genai

The setting for this variable is managed by OCI and cannot be modified directly. To use the OCI Generative AI Service with MySQL HeatWave GenAI, MySQL HeatWave automatically sets this system variable for resource principal authentication. The default value of the variable is the compartment ID of the database system currently in use.

rapid_ml_genai_session

Specifies the ID of the compartment you want to use for accessing the OCI Generative AI service. If you do not want to use the compartment ID of the DB system currently in use for accessing the OCI Generative AI service, then you can set this system variable to specify the ID of the compartment you want to use.

rapid_enable_my_sc

As of MySQL 9.4.1, controls whether statistics feedback from the InnoDB execution engine is used to improve query plans, particularly for queries with two or more joins and high MySQL costs. By injecting actual statistics from previous query executions into subsequent optimizations, MySQL HeatWave can produce more accurate and efficient plans, leading to significant performance improvements.

rapid_ap_stats_cache_max_entries

As of MySQL 9.4.1, controls the size of the HashMap used to control statistics feedback. Setting to 0 disables statistics feedback. Lower values imply fewer statistics cached for feedback.

rapid_hnsw_ef_search

As of MySQL 9.5.0, controls the accuracy of query results using the vector index. To disable the usage of HNSW indexes, you can set this session variable to 0.

rapid_hnsw_use_adaptive_accuracy_estimation

As of MySQL 9.5.0, controls adaptive accuracy estimation for similarity search queries that use the vector indexes.

rapid_auto_vector_index_enabled

As of MySQL 9.5.0, controls automatic vector index creation for frequently queried vector store columns. If disabled, all automatically created indexes are removed and no more automatic index creation happens until this variable is enabled.

rapid_auto_vector_index_interval_seconds

As of MySQL 9.5.0, specifies the time interval, in seconds, for automatically creating the vector indexes for frequently queried vector store columns.

rapid_auto_vector_index_server_memory_quota_pct

As of MySQL 9.5.0, specifies the maximum memory percentage that can be used by created indexes. Less beneficial indexes are removed if memory limits are exceeded, making space for more beneficial indexes.

rapid_auto_vector_index_skip_quiet_check

As of MySQL 9.5.0, controls whether MySQL HeatWave checks if the system is quiet before automatic vector index creation is started.

A quit system is:

This variable cannot be modified when RAPID is not bootstrapped.

rapid_auto_vector_index_build_timeout_seconds

As of MySQL 9.5.0, specifies the timeout duration, in seconds, for automatic vector index creation.

This variable cannot be modified when RAPID is not bootstrapped.

secondary_engine_cost_threshold

Defines the cost estimate threshold for offloading queries to the secondary engine. A query with a cost estimate on the primary engine that is higher than the threshold value is considered for execution on the secondary engine.

show_create_table_skip_secondary_engine

Whether to exclude the SECONDARY ENGINE clause from SHOW CREATE TABLE output, and from CREATE TABLE statements dumped by the mysqldump utility.

mysqldump provides the --show-create-skip-secondary-engine option. When specified, it enables the show_create_table_skip_secondary_engine system variable for the duration of the dump operation.

use_secondary_engine

Whether to execute queries using the secondary engine. These values are permitted:

external_table_storage_engine

Determines which engines are used for external tables.

rapid_ml_concurrency

Allows concurrent query processing for MySQL HeatWave AutoML and MySQL HeatWave GenAI as of MySQL 9.4.1. It can have a value between 1 and 8. The default value is 8. A value over 1 allows for concurrent query processing.

We recommend not enabling concurrent query processing with the following DB System shapes:

rapid_ace_auto_train_enabled

As of MySQL 9.4.2, enables or disables Advanced Cardinality Estimation (ACE) auto-training, which periodically runs in the background and manages rebuilding stale ACE models for loaded tables. See Analyze Tables.

rapid_ace_auto_train_interval_seconds

As of MySQL 9.4.2, determines the time (in seconds) between runs of ACE auto-training. See Analyze Tables.

rapid_ace_auto_train_max_execution_seconds

As of MySQL 9.4.2, determines the maximum amount of time in seconds ACE auto-training runs before stopping and completing early. See Analyze Tables.