 For example:

ALTER TABLE partitioned_table CONVERT PARTITION part1 TO TABLE normal_table;

CONVERT PARTITION will take an existing table and move this to another table
as its own partition with a specified partition definition. For example the
following moves normal_table to a partition of partitioned_table with a
definition that its values, based on the PARTITION BY of the
partitioned_table, are less than 12345.

ALTER TABLE partitioned_table CONVERT TABLE normal_table 
 TO PARTITION part1 VALUES LESS THAN (12345);

From MariaDB 11.4, the optional [{WITH | WITHOUT} VALIDATION] is permitted.

See Partitioning Overview: Converting Partitions to/from Tables for more
details.

See also 10.7 preview feature: CONVERT PARTITION (mariadb.org blog post)

DROP PARTITION
--------------

Used to drop specific partitions (and discard all data within the specified
partitions) for RANGE and LIST partitions. See Partitioning Overview: Dropping
Partitions.

EXCHANGE PARTITION
------------------

This is used to exchange the contents of a partition with another table. This
is performed by swapping the tablespaces of the partition with the other table.

From MariaDB 11.4, the optional [{WITH | WITHOUT} VALIDATION] is permitted.

See Partitioning Overview: Exchanging Partitions for more details.

See also copying InnoDB's transportable tablespaces.

OPTIMIZE PARTITION
------------------

See Partitioning Overview: Optimizing Partitions for details.

REMOVE PARTITIONING
-------------------

See Partitioning Overview: Removing Partitioning.

REORGANIZE PARTITION
--------------------

See Partitioning Overview: Reorganizing Partitions.

TRUNCATE PARTITION
------------------

See Partitioning Overview: Truncating Partitions.

DISCARD TABLESPACE
------------------

This is used to discard an InnoDB table's tablespace.

See copying InnoDB's transportable tablespaces for more information.

IMPORT TABLESPACE
-----------------

This is used to import an InnoDB table's tablespace. The tablespace should
have been copied from its original server after executing FLUSH TABLES FOR
EXPORT.

See copying InnoDB's transportable tablespaces for more information.

ALTER TABLE ... IMPORT only applies to InnoDB tables. Most other popular
storage engines, such as Aria and MyISAM, will recognize their data files as
soon as they've been placed in the proper directory under the datadir, and no
special DDL is required to import them.

ALGORITHM
---------

The ALTER TABLE statement supports the ALGORITHM clause. This clause is one of
the clauses that is used to implement online DDL. ALTER TABLE supports several
different algorithms. An algorithm can be explicitly chosen for an ALTER TABLE
operation by setting the ALGORITHM clause. The supported values are:

* ALGORITHM=DEFAULT - This implies the default behavior for the specific
statement, such as if no ALGORITHM clause is specified.
* ALGORITHM=COPY
* ALGORITHM=INPLACE
* ALGORITHM=NOCOPY - This was added in MariaDB 10.3.7.
* ALGORITHM=INSTANT - This was added in MariaDB 10.3.7.

See InnoDB Online DDL Overview: ALGORITHM for information on how the ALGORITHM
clause affects InnoDB.

ALGORITHM=DEFAULT
-----------------

The default behavior, which occurs if ALGORITHM=DEFAULT is specified, or if
ALGORITHM is not specified at all, usually only makes a copy if the operation
doesn't support being done in-place at all. In this case, the most efficient
available algorithm will usually be used.

However, in MariaDB 10.3.6 and before, if the value of the old_alter_table
system variable is set to ON, then the default behavior is to perform ALTER
TABLE operations by making a copy of the table using the old algorithm.

In MariaDB 10.3.7 and later, the old_alter_table system variable is
deprecated. Instead, the alter_algorithm system variable defines the default
algorithm for ALTER TABLE operations.

ALGORITHM=COPY
--------------

ALGORITHM=COPY is the name for the original ALTER TABLE algorithm from early
MariaDB versions.

When ALGORITHM=COPY is set, MariaDB essentially does the following operations:

-- Create a temporary t