[MDEV-24939] Detect incompatible MySQL virtual columns and report in error log. Created: 2021-01-06  Updated: 2023-11-30

Status: Open
Project: MariaDB Server
Component/s: Data Definition - Create Table
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Juan Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Compatibility, Migration, MySQL


 Description   

MariaDB does not support migration from MySQL-generated physical database tables containing virtual columns, and produces column mismatch errors, failures in mysql_upgrade, and InnoDB data dictionary inconsistencies where the tablename appears in "show tables;" but when selected produces error 1932.

2021-01-04 12:00:30 6 [Warning] InnoDB: Table test/REDACTED contains 11 user defined columns in InnoDB, but 10 columns in MariaDB. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
 
2021-01-04 12:00:30 6 [ERROR] mariadbd: Table 'REDACTED' is marked as crashed and should be repaired
 
2021-01-04 12:00:30 6 [ERROR] InnoDB: Table `test`.`REDACTED` is corrupted. Please drop the table and recreate.

mysql_upgrade:

test.REDACTED
 
Error : Table 'REDACTED' is marked as crashed and should be repaired
 
error : Corrupt
 

MariaDB [test]> show tables;
 
+----------------+
 
| Tables_in_test |
 
+----------------+
 
| Customers |
 
| REDACTED |
 
| simple |
 
| vw_simple |
 
+----------------+
 
4 rows in set (0.000 sec)
 
 
 
MariaDB [test]> select * from REDACTED;
 
ERROR 1932 (42S02): Table 'test.REDACTED' doesn't exist in engine

It would be very helpful for administrators if they could see a message when these errors happen letting them know that InnoDB has encountered an incompatible and unsupported table type, and recommend starting over with the corrupted tabled dumped logically and then dropped from the source.
Generated at Thu Feb 08 09:33:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.