MySQL HeatWave on OCI does not support
LOAD DATAwithALGORITHM=BULK.MySQL HeatWave on AWS does support
LOAD DATAwithALGORITHM=BULK, but does not support theINFILEandURLclauses.For versions earlier than MySQL 9.4.0, tables must have a primary key, and the primary key must not have a prefix index. For MySQL 9.4.0 and later, primary keys are not required.
-
LOAD DATAwithALGORITHM=BULKhas the following limitations:It locks the target table exclusively and does not allow other operations on the table.
It does not support automatic rounding or truncation of the input data. It fails if the input data requires rounding or truncation in order to be loaded.
It does not support temporary tables.
It is atomic but not transactional. It commits any transaction that is already running. On failure the
LOAD DATAstatement is completely rolled back.It cannot execute when the target table is explicitly locked by a
LOCK TABLESstatement.
-
The target table for
LOAD DATAwithALGORITHM=BULKhas the following limitations:It must be empty. The state of the table should be as though it has been freshly created. If the table has instantly added/dropped column, call TRUNCATE before calling
LOAD DATAwithALGORITHM=BULK.It must not be partitioned.
It must not contain secondary indexes. As of MySQL 9.2.0,
LOAD DATAwithALGORITHM=BULKdoes support secondary indexes.It must be in a file_per_tablespace, and must not be in a shared tablespace.
It must have the default row format,
ROW_FORMAT=DYNAMIC. UseALTER TABLEto make any changes to the table afterLOAD DATAwithALGORITHM=BULK.It must not contain virtual or stored generated columns.
It must not contain foreign keys.
It must not contain
CHECKconstraints.It must not contain triggers.
It is not replicated to other nodes.
It must not use a secondary engine. Set the secondary engine after
LOAD DATAwithALGORITHM=BULK. See: Section 4.2.6.2, “Define the Secondary Engine”.