-
Type:
Bug
-
Status: Confirmed (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.4
-
Fix Version/s: 10.4
-
Component/s: Storage Engine - InnoDB
-
Labels:
After the MDEV-18295 fix, IMPORT TABLESPACE will fail to import data files on which columns have been instantly reordered or dropped (MDEV-15562).
The problem is demonstrated by this part of the test innodb.instant_alter_import:
--echo # Import a data file that contains instant DROP COLUMN metadata
|
alter table t2 drop x; |
alter table t1 drop x, force; |
alter table t1 discard tablespace; |
|
flush tables t2 for export; |
--move_file $MYSQLD_DATADIR/test/t2.cfg $MYSQLD_DATADIR/test/t1.cfg
|
--copy_file $MYSQLD_DATADIR/test/t2.ibd $MYSQLD_DATADIR/test/t1.ibd
|
unlock tables;
|
|
--error ER_TABLE_SCHEMA_MISMATCH
|
alter table t1 import tablespace; |
The IMPORT TABLESPACE code should read the metadata record and the metadata BLOB early, to augment the metadata. Because the pages have not been adjusted yet, the buffer pool will have to be bypassed while reading the pages.
- blocks
-
MDEV-18762 Support easy restore of partial backup
-
- Stalled
-
-
MDEV-23874 Crash in ALTER TABLE ... IMPORT TABLESPACE for the table after instant ALTER was used on it
-
- Open
-
- is caused by
-
MDEV-15562 Instant DROP COLUMN or changing the order of columns
-
- Closed
-
- relates to
-
MDEV-20590 Introduce a file format constraint to ALTER TABLE
-
- Closed
-
-
MDEV-21549 IMPORT TABLESPACE fails to adjust all tablespace ID in root pages
-
- Closed
-
-
MDEV-18295 IMPORT TABLESPACE fails with instant-altered tables
-
- Closed
-