[MDEV-23106] Unable to recognize/import partitioned tables from physical MySQL databases. Created: 2020-07-06 Updated: 2023-06-25 Resolved: 2023-06-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Partitioning, Storage Engine - InnoDB |
| Affects Version/s: | 10.4.13, 10.5.4 |
| Fix Version/s: | 10.8.8, 10.6.15, 10.9.8, 10.10.6, 10.11.5, 11.0.3, 11.1.2, 11.2.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Juan | Assignee: | Michael Widenius |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | compat57, innodb, partitioning | ||
| Environment: |
CentOS 7 |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
In MySQL 5.7:
Stop server & physically copy datadir, or remove MySQL binaries & replace with MariaDB binaries.
Try running mysql_upgrade:
Problem confirmed with tables partitioned by HASH, COLUMN, KEY, RANGE, and LIST. |
| Comments |
| Comment by Sergei Golubchik [ 2020-07-08 ] | ||||||||||||
|
is it native innodb partitioning? what's the content of the datadir? | ||||||||||||
| Comment by Elena Stepanova [ 2020-07-08 ] | ||||||||||||
|
Yes, I assume it's native InnoDB partitioning. No .par file in the datadir. | ||||||||||||
| Comment by Sergei Golubchik [ 2020-07-11 ] | ||||||||||||
|
MariaDB does not support InnoDB native partitioning | ||||||||||||
| Comment by Michael Widenius [ 2023-06-01 ] | ||||||||||||
|
Reopened the bug as we now have a solution for this problem | ||||||||||||
| Comment by Michael Widenius [ 2023-06-01 ] | ||||||||||||
|
The problem with MySQL partitions compared to MariaDB partitions is two fold:
The MySQL InnoDB data on disk seams to be identical to MariaDB's, which means that in theory it is possible to 'instantly' convert a partitioned MySQL table to MariaDB. I have now been able to provide a fix for the above issues:
| ||||||||||||
| Comment by Michael Widenius [ 2023-06-25 ] | ||||||||||||
|
Pushed to 10.6 tree |