[MDEV-10433] ALTER ONLINE TABLE reported as not supported for TokuDB table Created: 2016-07-25 Updated: 2022-09-12 Resolved: 2022-09-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | OTHER |
| Affects Version/s: | 10.0 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | jocelyn fournier | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hi, When I try to run an ALTER ONLINE TABLE my_table ADD KEY my_key (...) on a TokuDB table, it reports However, ONLINE is supported, and it's an online operation which is applied when the syntax To repeat :
It would be great to have a consistent behaviour in MariaDB. Thanks and regards, |
| Comments |
| Comment by Sergei Golubchik [ 2016-07-26 ] |
|
It depends on how you define "online". As you can see from the error message, ONLINE means LOCK=NONE. Also, in the manual:
When TokuDB adds indexes, the table cannot be modified, it supports LOCK=SHARED, but not LOCK=NONE. So it's not always online. You can specify LOCK=SHARED as the error message suggests, then it'll work. |
| Comment by jocelyn fournier [ 2016-07-26 ] |
|
Hi Sergei, When I use CREATE INDEX on a TokuDB table, with tokudb_create_index_online=ON, the table can be modified while creating the index, it doesn't lock anything, and allows concurrent DML (verified when I had to add an index on a big table during more than 1h, and a lot of INSERT / UPDATE in parallel). So it seems to be ONLINE with LOCK=NONE. Thanks, |
| Comment by Sergei Golubchik [ 2022-09-12 ] |
|
10.0 was EOLed in March 2019 |