7 Manage HeatWave Data with Workspaces

The Workspaces page in the MySQL HeatWave Console permits loading data into or unloading data from a HeatWave Cluster. Load and unload operations are performed using Auto Parallel Load, which optimizes operation time and memory usage by predicting an using an optimal degree of parallelism. Data is loaded into HeatWave from the associated DB System. If you have not loaded data into your DB System, see Importing Data.

The MySQL user that is performing the load or unload operation must have the following MySQL privileges:

• The PROCESS privilege.

• The EXECUTE privilege on the sys schema.

• The SELECT privilege on the Performance Schema.

The time required to load data from the DB System into the HeatWave Cluster depends on the data size.

Note:

HeatWave Cluster data can also be managed using SQL or the Auto Parallel Load interface from a MySQL client. For more information, Loading Data, in the MySQL HeatWave User Guide.

To load data:

1. Connect to a DB System that has a HeatWave Cluster. For instructions, see Connecting from the Console.

2. Under Select tables to unload or load into HeatWave, select the schemas and tables that you want to load or unload. Selecting a schema selects all of the schema's tables. Expanding a table row using the drop-down control reveals the table's columns. The Load Status column provides the load status as a percentage value.

3. Optionally, enable the Detail View to view additional information about schemas and tables. Details include:

   • Name: The name of the schema or table

   • Memory Size Estimate (GiB): An estimate of the memory required on the HeatWave Cluster for the schema or table

   • Rows Estimate: The estimated number of rows in the table

   • Load Status: The load status of the table as a percentage value. You can click the refresh icon to refresh the load status.

   • String Column Encoding: The number of columns to be encoded as VARLEN (variable-length) columns, expressed as a fraction of the total number of table columns. For information about HeatWave string column encoding, see Encoding String Columns, in the HeatWave User Guide.

   • Predicted Load Time (s): The predicted load time in seconds

4. After you have selected the tables you want to load or unload, click Load or Unload.

   If loading data, the MySQL Auto Parallel Load tables into HeatWave dialog appears, providing a summary of the load operation to be executed. The following information is shown:

   • DB System: The DB System name

   • Estimated load size: The estimated size of the data to be loaded

   • Estimated load time: The estimated time required to load the data

   • Selected schemas and tables: The selected schemas and tables to be loaded

     • Name: Name of the schema or table

     • Memory Size Estimate (GiB): The memory size estimate for the schema or table on the HeatWave Cluster

   • Estimated total memory footprint: A pie chart showing the estimated percentage of HeatWave Cluster memory required for each table

   • Estimated load times (seconds): A pie chart showing estimated load times for each table

   If unloading data, the MySQL Auto Parallel Unload tables from HeatWave dialog appears, providing a summary of the unload operation to be executed. The following information is shown:

   • DB System: The name of the DB System

   • Estimated unload size: The estimated size of the data to be unloaded

   • Selected schemas and tables: The selected schema and tables to be unloaded

     • Name: Name of the schema or table

     • Memory Size Estimate (GiB): The memory size estimate for the schema or table on the HeatWave Cluster

   • Estimated memory foot print (GiB): The estimated HeatWave Cluster memory footprint showing occupied memory, current free memory, and additional available free memory after the unload operation

5. Click Confirm Load or Confirm Unload to start the load or unload operation.

The Cluster Memory Snapshot shows the amount of HeatWave Cluster memory used.