bb-10.8-mdev-27106 : lp:maria : Git : Code : MariaDB

Get this branch:: git clone -b bb-10.8-mdev-27106 https://git.launchpad.net/maria

Branch merges

Branch information

Name:: bb-10.8-mdev-27106

Repository:: lp:maria

Recent commits

384f9d3... by Nayuta Yanagisawa on 2021-11-25

MDEV-27106 Spider: specify connection to data node by engine-defined attributes

We introduce engine-defined attributes to specify remote data nodes.

The engine attributes do not cover all the existing DSN parameters
because most of them need not be specified at the table level.
We introduce the following three attributes: REMOTE_SERVER,
REMOTE_DATABASE, REMOTE_TABLE.

One cannot specify both DSN parameter, in COMMENT or CONNECT, and
engine-defined attribute that are for the same SPIDER_SHARE attribute.
For example, Spider returns an error if both COMMENT='table "t1"'
and REMOTE_TABLE="t2" are specified for a single Spider table or
a single partition in a Spider table.

432e591... by Nayuta Yanagisawa on 2021-11-30

MDEV-5271 Support engine-defined attributes per partition

Make it possible to specify engine-defined attributes on partitions
as well as tables.

If an engine-defined attribute is only specified at the table level,
it applies to all the partitions in the table.
This is a backward-compatible behavior.

If the same attribute is specified both at the table level and the
partition level, the per-partition one takes precedence.
So, we can consider per-table attributes as default values.

One cannot specify engine-defined attributes on subpartitions.

Implementation details:

* We store per-partition attributes in the partition_element class
because we already have the part_comment field, which is for
per-partition comments.

* In the case of ALTER TABLE statements, the partition_elements in
table->part_info is set up by mysql_unpack_partition().
So, we parse per-partition attributes after the call of the function.

897d8c5... by Marko Mäkelä on 2021-11-29