Details
Critical
Description
The doc state
The DDL syntax is different. While binaries from Tokutek have the patched SQL parser, TokuDB in MariaDB uses the special Storage Engine API extension. Thus in Tokutek binaries you write CLUSTERED KEY (columns) and, for example, ROW_FORMAT=TOKUDB_LZMA. And in MariaDB you write KEY (columns) CLUSTERING=YES and COMPRESSION=TOKUDB_LZMA.
But it looks that alter table does not follow documented rules.
MariaDB [tyrebase4W]> alter table t_price_multi drop index date, add primary key (date,id), engine=tokudb compression=tokudb_lzma; ERROR 1911 (HY000): Unknown option 'compression'
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
works for me, no syntax error, the table is altered as expected.
I think the problem is that you change the engine and in the same statement set attributes (compression) specific to the new engine. I'd guess that the server looks in the old storage engine to see whether an attribute is supported, not in the new.