Search Results
https://dev.mysql.com/doc/heatwave/en/mys-hw-insert-select.html
This topic describes how to run a SELECT query and insert the results into a target table using the INSERT ... The target table can be an InnoDB table and does not need to use a secondary engine. When the query is offloaded to MySQL HeatWave, it is ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-auto-loading-data.html
You can use Auto Parallel Load to load data from Object Storage into MySQL HeatWave Cluster. Since no dialect parameters are included, Lakehouse loads a CSV file by default with all default settings. mysql> CALL sys.HEATWAVE_LOAD( '[{"db_name": ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-export-query-result-par-redact.html
It also displays the latest query results from the query text from the performance_schema.rpd_query_stats table and retrieves all the MySQL statments currently being executed in all MySQL active connections on the network. The pre-authenticated ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-incremental-load.html
Available as of MySQL 9.0.0, Lakehouse Incremental Load allows you to refresh the data in an external table. This topic contains the following sections: Before You Begin Refresh Data Overview Perform Initial Load Refresh Data What's Next Before You ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-limitations-all.html
The following options for the CREATE TABLE statement: AUTOEXTEND_SIZE AVG_ROW_LENGTH CHECKSUM COMPRESS CONNECTION DATADIR DELAY_KEY_WRITE ENCRYPT INDEXDIR INSERT_METHOD KEY_BLOCK_SIZE MAX_ROWS MIN_ROWS PACK_KEYS PASSWORD ROW_FORMAT STATS_AUTO_RECALC ... MySQL HeatWave Lakehouse has the following limitations for all file ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-loading-data-manually-how-to.html
If you choose not to Load Structured Data Using Lakehouse Auto Parallel Load, you can load external data manually. CREATE TABLE Statement Depending on the version of MySQL you are using, use the appropriate CREATE TABLE statement. As of MySQL ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-metadata-queries-query-history.html
CONNECTION_ID The connection ID of the client that issued the query. To view the MySQL HeatWave query history including query start time, end time, and wait time in the scheduling queue, as discussed in Section 5.4.10, “Auto Scheduling”.
https://dev.mysql.com/doc/heatwave/en/mys-hw-partitioning.html
When data is loaded into MySQL HeatWave, it is partitioned by the table primary key and sliced horizontally for distribution among MySQL HeatWave nodes by default. To use this feature, define data placement keys on the most frequently used JOIN ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-query-runtimes.html
This topic describes how you can view MySQL HeatWave query runtimes and runtime estimates using the MySQL HeatWave Autopilot Advisor Auto Query Time Estimation feature, or by querying the performance_schema.rpd_query_stats table. Runtime data is ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-rpd-query-stats-table.html
The rpd_query_stats table has these columns: CONNECTION_ID The ID of the connection. The rpd_query_stats table stores query compilation and execution statistics produced by the MySQL HeatWave plugin in JSON format. For MySQL HeatWave AutoML ...