Import Dump with InnoDB Fulltext Index and Constraint fails

[Jeroen Smit]

After having deployed a new machine with a clean installation of percona 5.7.10-3 we ran into issues with importing some of our database dumps. These dumps could be imported without fail on percona 5.6.27.

Issue is due to a combination of full text and constraints.
Bug was also reported and reported fixed in MySQL 5.7.11 / 5.8 (as per https://bugs.mysql.com/bug.php?id=78955)

Copied the steps to reproduce as described in the original report.

Following SQL fails with: ERROR 1215 (HY000) at line 2: Cannot add foreign key constraint

SET FOREIGN_KEY_CHECKS = 0;
CREATE TABLE `table` (
  `node` int(10) unsigned NOT NULL,
  `index` longtext,
  PRIMARY KEY (`node`),
  FULLTEXT KEY `index` (`index`),
  FOREIGN KEY (`node`) REFERENCES `node` (`node`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB;

Whereas the following runs without fail

SET FOREIGN_KEY_CHECKS = 0;
CREATE TABLE `table` (
  `node` int(10) unsigned NOT NULL,
  `index` longtext,
  PRIMARY KEY (`node`),
  FOREIGN KEY (`node`) REFERENCES `node` (`node`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB;

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3389