2.2.2 Loading Data Manually

2.2.2.1 Excluding Table Columns

2.2.2.2 Defining the Secondary Engine

2.2.2.3 Loading Tables

2.2.2.4 Loading Partitions

As of MySQL 9.1.0, HeatWave supports InnoDB partitions. Selectively loading and unloading partitions will reduce memory requirements. The use of partition information can allow data-skipping and accelerate query processing.

HeatWave Guided Load uses HeatWave Autopilot to exclude schemas, tables, and columns that cannot be loaded, and define RAPID as the secondary engine. To load data manually, follow these steps:

1. Optionally, applying string column encoding and data placement workload optimizations. For more information, see Section 2.7, “Workload Optimization for OLAP”.

2. Loading tables or partitions using ALTER TABLE ... SECONDARY_LOAD statements. See Section 2.2.2.3, “Loading Tables” and Section 2.2.2.4, “Loading Partitions”.

3. As of MySQL 9.1.0, to prevent Auto Parallel Load from automatically loading a table, define the secondary engine as something other than RAPID, see: Section 2.2.2.2, “Defining the Secondary Engine”.