Bug #84158 Loading table with fulltext from mysqldump fails

• Submitted: 11 Dec 2016 12:15
• Modified: 12 Dec 2016 5:18
• Reporter: Daniël van Eeden (OCA)
• Status: Verified
• Category: MySQL Server: mysqldump Command-line Client
• Severity: S3 (Non-critical)
• Version: 8.0.0, 5.7.16
• OS: Any
• CPU Architecture: Any
• Tags: fts, fulltext

[11 Dec 2016 12:15] Daniël van Eeden

Description:
Dumping a large table with FTS goes without issue (5.7.15 mysqldump)
Then loading into 8.0.0 fails.

It does work if I use --skip-extended-insert

Related:
Bug #83397 	INSERT INTO ... SELECT FROM ... fails if source has > 65535 rows on FTS

How to repeat:
See description and attachments

[11 Dec 2016 12:17] Daniël van Eeden

dump file

Attachment: bug84158_phone.sql.xz (application/x-xz, text), 879.97 KiB.

[11 Dec 2016 12:18] Daniël van Eeden

dump file w/o extended

Attachment: bug84158_phone_2.sql.xz (application/x-xz, text), 369.66 KiB.

[12 Dec 2016 5:18] MySQL Verification Team

Hello Daniël,

Thank you for the report.
Observed this with 5.7.16 builds.

Thanks,
Umesh

[12 Dec 2016 5:20] MySQL Verification Team

-- 5.7.16

-- restored dump taken with --skip-extended-insert
-- taken dump - no issues
[umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.7.16: bin/mysqldump -uroot -S /tmp/mysql_ushastry.sock --databases test > test.sql

-- import
[umshastr@hod03]/export/umesh/server/binaries/GABuilds/mysql-5.7.16: bin/mysql -uroot -S /tmp/mysql_ushastry.sock test < test.sql
ERROR 182 (HY000) at line 49: Invalid InnoDB FTS Doc ID

[26 Sep 2017 12:28] Naga Satyanarayana Bodapati

Posted by developer:
 
This is 5.7 bug and also exists in 8.0 (nothing has changed in FTS area in 8.0)

Requesting to remove SR80RC and put appropriate tag