Search Results
https://dev.mysql.com/doc/heatwave/en/mys-hw-advisor-data-placement.html
Data placement keys are used to partition table data among MySQL HeatWave nodes when loading tables. Partitioning table data by JOIN and GROUP BY key columns can improve query performance by avoiding costs associated with redistributing data among ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-async-apptask-list.html
offset (INT UNSIGNED): specifies the initial number of tasks to skip. The app_task_list routine returns a paginated list of asynchronous tasks associated with an application user. This topic contains the following sections: Syntax Syntax Example ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-async-apptask-status-list.html
offset (INT UNSIGNED): specifies the initial number of rows to skip. The app_task_status_list routine returns a paginated list of application task statuses. This topic contains the following sections: Syntax Syntax Example See Also Syntax mysql> ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-async-exec-prepared-stmt-app.html
app_user_id (VARCHAR(255)): specifies the unique ID of the application user initiating the task. You can set this to NULL if no specific structure definition is required for the task data. You can set this parameter to NULL if no specific structure ... The execute_prepared_stmt_from_app_async routine creates an asynchronous task associated with a specific application ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-async-task-status-list.html
offset (INT UNSIGNED): specifies the initial number of rows to skip. The task_status_list routine returns a paginated list of task statuses. This topic contains the following sections: Syntax Syntax Example See Also Syntax mysql> SELECT ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-autopilot-report-table.html
It contains data from the last execution of Advisor or Auto Parallel Load. Data is only available for the current session and is lost when the session terminates or when the server shuts down. When Advisor or Auto Parallel Load run, they send ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-change-propagation.html
After tables are loaded into MySQL HeatWave, data changes are automatically propagated from DB System tables to their counterpart tables in the MySQL HeatWave Cluster. DML operations, INSERT, UPDATE, and DELETE, on the DB System do not wait for ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-create-temp-table.html
Reusing the temporary table across multiple reports balances the initial creation cost. As of MySQL 9.3.0, you can create temporary tables that are stored in the MySQL HeatWave Cluster. A temporary table is visible only within the current session, ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-auto-parallel-load-overview.html
Lakehouse Auto Parallel Load also includes Lakehouse Incremental Load, which can refresh tables after an initial load. If the inferred data type is incompatible with the table definition, Lakehouse Auto Parallel Load raises an error, and specifies ... Lakehouse Auto Parallel Load, which extends the Auto Parallel Load feature of MySQL HeatWave, facilitates the process of loading data from Object Storage into MySQL HeatWave by automating many of the steps involved, including: Excluding schemas, tables, and columns that Auto Parallel Load cannot ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-load-event-based.html
For the initial load, you must specify at least one external file location with the file or FILES option. As of MySQL 9.4.1, you can load data from Object Storage by using event-based incremental load. Once an event for an external file location is ...