mirror of
https://github.com/MariaDB/server.git
synced 2025-11-25 17:25:02 +03:00
eca5c2c67f
MDEV-22088 S3 partitioning support
All ALTER PARTITION commands should now work on S3 tables except
REBUILD PARTITION
TRUNCATE PARTITION
REORGANIZE PARTITION
In addition, PARTIONED S3 TABLES can also be replicated.
This is achived by storing the partition tables .frm and .par file on S3
for partitioned shared (S3) tables.
The discovery methods are enchanced by allowing engines that supports
discovery to also support of the partitioned tables .frm and .par file
Things in more detail
- The .frm and .par files of partitioned tables are stored in S3 and kept
in sync.
- Added hton callback create_partitioning_metadata to inform handler
that metadata for a partitoned file has changed
- Added back handler::discover_check_version() to be able to check if
a table's or a part table's definition has changed.
- Added handler::check_if_updates_are_ignored(). Needed for partitioning.
- Renamed rebind() -> rebind_psi(), as it was before.
- Changed CHF_xxx hadnler flags to an enum
- Changed some checks from using table->file->ht to use
table->file->partition_ht() to get discovery to work with partitioning.
- If TABLE_SHARE::init_from_binary_frm_image() fails, ensure that we
don't leave any .frm or .par files around.
- Fixed that writefrm() doesn't leave unusable .frm files around
- Appended extension to path for writefrm() to be able to reuse to function
for creating .par files.
- Added DBUG_PUSH("") to a a few functions that caused a lot of not
critical tracing.
81 lines
1.9 KiB
Plaintext
81 lines
1.9 KiB
Plaintext
--source include/have_partition.inc
|
|
--source include/have_innodb.inc
|
|
--source include/have_s3.inc
|
|
--source include/have_sequence.inc
|
|
--source create_database.inc
|
|
|
|
#
|
|
# The purpose of this test is to show how to move an partition from an existing
|
|
# InnoDB partitioned table (t1) to a partitioned table in S3 (archive)
|
|
#
|
|
|
|
#
|
|
# We start by creating a partioned table in S3 with one existing partion p0
|
|
#
|
|
|
|
CREATE TABLE p0 (
|
|
c1 int primary key,
|
|
c2 int DEFAULT NULL
|
|
) ENGINE=InnoDB;
|
|
insert into p0 select seq,seq from seq_1_to_99;
|
|
|
|
alter table p0 engine=s3 , rename to archive
|
|
PARTITION BY RANGE (c1)
|
|
(PARTITION p0 VALUES LESS THAN (100));
|
|
|
|
show create table archive;
|
|
|
|
#
|
|
# Then we create the table t1 that contains multiple partitions.
|
|
# Partition p1 is the one that we want to move to 'archive'
|
|
#
|
|
|
|
CREATE TABLE t1 (
|
|
c1 int primary key,
|
|
c2 int DEFAULT NULL
|
|
) ENGINE=InnoDB
|
|
PARTITION BY RANGE (c1)
|
|
(PARTITION p1 VALUES LESS THAN (200),
|
|
PARTITION p2 VALUES LESS THAN (300),
|
|
PARTITION p3 VALUES LESS THAN (400));
|
|
insert into t1 select seq,seq from seq_100_to_399;
|
|
|
|
#
|
|
# Then it's time to do the real work.
|
|
#
|
|
|
|
# First we move partition p1 to a normal InnoDB table
|
|
|
|
create table p1 like t1;
|
|
alter table p1 remove partitioning;
|
|
alter table t1 exchange partition p1 with table p1;
|
|
alter table t1 drop partition p1;
|
|
|
|
show create table p1;
|
|
select count(*) from p1;
|
|
|
|
# Then change the table engine to s3 and move it into archive
|
|
|
|
alter table p1 engine=s3;
|
|
alter table archive add partition (partition p1 values less than (200));
|
|
alter table archive exchange partition p1 with table p1;
|
|
|
|
# p1 will be empty as this was the new partition that we just created
|
|
select count(*) from p1;
|
|
drop table p1;
|
|
|
|
#
|
|
# The p1 partition has now been moved from t1 to archive. Check the result
|
|
#
|
|
|
|
show create table t1;
|
|
show create table archive;
|
|
select count(*) from t1;
|
|
select count(*) from archive;
|
|
drop table t1,archive;
|
|
|
|
#
|
|
# clean up
|
|
#
|
|
--source drop_database.inc
|