[MDEV-6335] Difference in TokuDB engine DDL makes sql dumps incompatible. Created: 2014-06-12  Updated: 2014-06-20  Resolved: 2014-06-20

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.12
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Alexey Zilber Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

CentOs 6.x, TokuDB 7.1.6, MariaDB 10.0.11


 Description   

Because of the difference in DDL syntax between TokuTek's TokuDB and MariaDB, mysql dumps are incompatible. This is because one uses ROW_FORMAT and the other COMPRESSION.

This is a pretty awful situation to be in. Essentially, we're stuck with either one or the other because of the huge amount of data we have.

There should at least be some aliasing or workaround for this.

 Comments   
Comment by Elena Stepanova [ 2014-06-20 ]

This is a duplicate of MDEV-5571.
Quoting the comment by serg from there:

There isn't much we can do. mysqldump output is perfectly compatible between mariadb-5.5 and mariadb-10.0. It is not compatible with tokutek-patched releases.
As a workaround, you could edit the dump, replacing "ROW_FORMAT=TOKUDB" with "COMPRESSION=TOKUDB". Or you can simply start MariaDB on the same datadir and generate the dump in MariaDB. Then it'll use correct MariaDB-compatible syntax.

Generated at Thu Feb 08 07:11:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.