mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01: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.
15 lines
422 B
Text
15 lines
422 B
Text
SET @saved_dbug = @@debug_dbug;
|
|
CREATE TABLE p0 (
|
|
c1 int primary key,
|
|
c2 int DEFAULT NULL
|
|
) ENGINE=InnoDB;
|
|
insert into p0 select seq,seq from seq_1_to_10;
|
|
SET debug_dbug='+d,failed_create_partitioning_metadata';
|
|
alter table p0 engine=s3
|
|
PARTITION BY RANGE (c1)
|
|
(PARTITION p0 VALUES LESS THAN (100));
|
|
ERROR HY000: Simulated crash
|
|
SET debug_dbug=@saved_dbug;
|
|
drop table p0;
|
|
drop table p0;
|
|
ERROR 42S02: Unknown table 's3.p0'
|