Bug #62576 Can't apply FULLTEXT on column for Innodb database

Submitted: 29 Sep 2011 22:12 Modified: 26 Nov 2011 9:14
Reporter: Neil Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: FULLTEXT search Severity:S3 (Non-critical)
Version:5.6 OS:Windows (2008 Standard)
Assigned to: CPU Architecture:Any
Tags: 5.6, fulltext, innodb, MySQL

[29 Sep 2011 22:12] Neil 
Description:
I downloaded MySQL 5.6 and tried to apply FULLTEXT index on a column, but get the error message ERROR 1214: The used table type doesn't support FULLTEXT indexes

How to repeat:
Create a new table with a Innodb database, and apply FULLTEXT index on a column.
[30 Sep 2011 17:40] Valeriy Kravchuk 
What exact version, 5.6.x, you had downloaded?
[30 Sep 2011 19:15] Neil 
I downloaded mysql-5.6.2-m5-win32.msi
[4 Oct 2011 19:41] Neil 
Do you need anymore information from me?
[10 Oct 2011 23:30] MySQL Verification Team 
Where you read that version has InnoDB Fulltext support?. Thanks.
[11 Oct 2011 13:51] Neil 
I found the feature from the article at http://www.oracle.com/us/corporate/press/439460
[26 Oct 2011 8:22] Neil 
Do you need any more information from me ?  It's been two weeks since my last reply ?
[26 Oct 2011 9:14] Valeriy Kravchuk 
Please, re-read that press release carefully. It mentions labs.mysql.com. So, please,go to that page and choose proper snapshot binaries for FULLTEXT support in InnoDB, mysql-5.6-labs-innodb-fts. Download and check with it.
[27 Nov 2011 7:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.057 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.