[MDEV-16499] [10.1] ER_NO_SUCH_TABLE_IN_ENGINE followed by "Please drop the table and recreate" upon adding FULLTEXT key to table with virtual column Created: 2018-06-15 Updated: 2019-01-14 Resolved: 2019-01-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table, Full-text Search, Storage Engine - InnoDB, Storage Engine - XtraDB, Virtual Columns |
| Affects Version/s: | 10.0, 10.1 |
| Fix Version/s: | 10.4.2, 10.1.38, 10.0.38, 10.2.22, 10.3.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Eugene Kosov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Not reproducible on 10.2. |
| Comments |
| Comment by Elena Stepanova [ 2018-07-07 ] | ||||||||||||||
|
Extra step in the same scenario brings an additional error message, adding it here to make it searchable and indicate it's a part of the same problem:
| ||||||||||||||
| Comment by Marko Mäkelä [ 2018-08-29 ] | ||||||||||||||
|
Before 10.2, InnoDB does not know anything about virtual columns. I feel that the creation of any indexes on virtual columns has to be blocked in the SQL layer, before allowing the execution to enter InnoDB, either ALGORITHM=INPLACE (like in this case) or ALGORITHM=COPY. Starting with 10.2, InnoDB correctly blocks attempts to create FULLTEXT or SPATIAL index on virtual columns. | ||||||||||||||
| Comment by Elena Stepanova [ 2018-08-29 ] | ||||||||||||||
|
Yes, except that in both cases above, the added index is NOT on a virtual column, and not even on the column it references, but on a third unrelated column. And there are no indexes on virtual columns at all, fulltext or not. | ||||||||||||||
| Comment by Marko Mäkelä [ 2019-01-14 ] | ||||||||||||||
|
This was a bogus error message. |