Fix "The used table type doesn't support FULLTEXT indexes" (ERROR 1214 (HY000))

If changing a table’s engine to InnoDB produces a FULLTEXT index problem like this:

ERROR 1214 (HY000): The used table type doesn't support FULLTEXT indexes

Inspect the table structure with the command below to find the names of FULLTEXT indexes so you can remove them. They must be removed because InnoDB does not support FULLTEXT indexes.

SHOW CREATE TABLE table1;

CREATE TABLE `table1` (
  `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'Coupons Id',
  `name` varchar(100) CHARACTER SET utf8 DEFAULT NULL COMMENT 'Coupons Name',
  `description` varchar(5000) CHARACTER SET utf8 DEFAULT NULL COMMENT 'Coupons Description',
  `date` datetime DEFAULT NULL COMMENT 'Coupons purchase start date',
  `status` varchar(3) CHARACTER SET utf8 DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `status` (`status`),
  FULLTEXT KEY `name` (`name`),
  FULLTEXT KEY `description` (`description`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 

The example above has two FULLTEXT indexes: name and description. Drop the FULLTEXT key indexes with the commands below so you can change the table engine to InnoDB.

ALTER TABLE table1 DROP INDEX name;
ALTER TABLE table1 DROP INDEX description;