has changed.
When set to 0, stats will be recalculated only when an ANALYZE TABLE is run.
If set to DEFAULT, or left out, the value set by the innodb_stats_auto_recalc
system variable applies. See InnoDB Persistent Statistics.

STATS_PERSISTENT
----------------

STATS_PERSISTENT indicates whether the InnoDB statistics created by ANALYZE
TABLE will remain on disk or not. It can be set to 1 (on disk), 0 (not on
disk, the pre-MariaDB 10 behavior), or DEFAULT (the same as leaving out the
option), in which case the value set by the innodb_stats_persistent system
variable will apply. Persistent statistics stored on disk allow the statistics
to survive server restarts, and provide better query plan stability. See
InnoDB Persistent Statistics.

STATS_SAMPLE_PAGES
------------------

STATS_SAMPLE_PAGES indicates how many pages are used to sample index
statistics. If 0 or DEFAULT, the default value, the innodb_stats_sample_pages
value is used. See InnoDB Persistent Statistics.

TRANSACTIONAL
-------------

TRANSACTIONAL is only applicable for Aria tables. In future Aria tables
created with this option will be fully transactional, but currently this
provides a form of crash protection. See Aria Storage Engine for more details.

UNION
-----

UNION must be specified when you create a MERGE table. This option contains a
comma-separated list of MyISAM tables which are accessed by the new table. The
list is enclosed between parenthesis. Example: UNION = (t1,t2)

WITH SYSTEM VERSIONING
----------------------

WITH SYSTEM VERSIONING is used for creating System-versioned tables.

Partitions
----------

partition_options:
  PARTITION BY
    { [LINEAR] HASH(expr)
    | [LINEAR] KEY(column_list)
    | RANGE(expr)
    | LIST(expr)
    | SYSTEM_TIME [INTERVAL time_quantity time_unit] [LIMIT num] }
  [PARTITIONS num]
  [SUBPARTITION BY
    { [LINEAR] HASH(expr)
    | [LINEAR] KEY(column_list) }
   [SUBPARTITIONS num]
  ]
  [(partition_definition [, partition_definition] ...)]
partition_definition:
  [PARTITION] partition_name
    [VALUES {LESS THAN {(expr) | MAXVALUE} | IN (value_list)}]
    [[STORAGE] ENGINE [=] engine_name]
    [COMMENT [=] 'comment_text' ]
    [DATA DIRECTORY [=] 'data_dir']
    [INDEX DIRECTORY [=] 'index_dir']
    [MAX_ROWS [=] max_number_of_rows]
    [MIN_ROWS [=] min_number_of_rows]
    [TABLESPACE [=] tablespace_name]
    [NODEGROUP [=] node_group_id]
    [(subpartition_definition [, subpartition_definition] ...)]
subpartition_definition:
  SUBPARTITION logical_name
    [[STORAGE] ENGINE [=] engine_name]
    [COMMENT [=] 'comment_text' ]
    [DATA DIRECTORY [=] 'data_dir']
    [INDEX DIRECTORY [=] 'index_dir']
    [MAX_ROWS [=] max_number_of_rows]
    [MIN_ROWS [=] min_number_of_rows]
    [TABLESPACE [=] tablespace_name]
    [NODEGROUP [=] node_group_id]
If the PARTITION BY clause is used, the table will be partitioned. A partition
method must be explicitly indicated for partitions and subpartitions.
Partition methods are:

* [LINEAR] HASH creates a hash key which will be used to read and write rows.
The partition function can be any valid SQL expression which returns an
INTEGER number. Thus, it is possible to use the HASH method on an integer
column, or on functions which accept integer columns as an argument. However,
VALUES LESS THAN and VALUES IN clauses can not be used with HASH. An example:

CREATE TABLE t1 (a INT, b CHAR(5), c DATETIME)
  PARTITION BY HASH ( YEAR(c) );

[LINEAR] HASH can be used for subpartitions, too.

* [LINEAR] KEY is similar to HASH, but the index has an even distribution of
data. Also, the expression can only be a column or a list of columns. VALUES
LESS THAN and VALUES IN clauses can not be used with KEY.
* RANGE partitions the rows using on a range of values, using the VALUES LESS
THAN operator. VALUES IN is not allowed with RANGE. The partition function can
be any valid SQL expression which returns a single value.
* LIST assigns partitions based on a table's column with a restricted set of
possible values. It is similar to RANGE, but VALUES IN must be used for at
least 1 columns, and ìä£