Schema mismatch when importing table with full-text index from xtrabackup backup

Description

This issue is the continuation of https://forums.percona.com/t/safe-to-import-backup-without-cfg/15931

 

When importing a single table (IMPORT TABLESPACE) from a backup made using xtrabackup and the table contains a full-text index the import process will error out with : 

MySQL and Xtrabackup versions : 

I was able to reproduce consistently the issue multiple times in test VMs and Docker containers using the official Oracle image.

Attached below is an archive with create statement, already prepared (with --export) idb & cfg files along with an import script to reproduce the issue.

 

Environment

None

Attachments

1

Smart Checklist

Activity

Show:

Satya Bodapati June 11, 2024 at 2:25 PM

This issue is fixed and will be part of the upcoming release 8.0.35-31.

Aaditya Dubey October 23, 2023 at 7:18 AM

Hi ,

Thank you for the updates regarding version, will check and update you.

Greg McLemore September 5, 2023 at 4:21 PM

It would be wonderful if the priority would be reconsidered, as this bug prevents table restoration.

Also, there is a link above that ties this as a duplicate of which is marked as 'done'.  As far as affected versions, I can confirm the bug still exists in the most current version as of today: 8.0.34-29 (2023-08-21).

Raphael Galmiche September 5, 2023 at 7:58 AM

Since this issue can block the import of entire tables from a backup perhaps the priority should be reconsidered ?

Greg McLemore September 4, 2023 at 11:06 PM

This has now been a known and reproducible issue for over a year.  If someone has a great workaround (until/if this is fix), please advise. Thank you. 

Done

Details

Assignee

Reporter

Planned Version/s

Sprint

Affects versions

Priority

Smart Checklist

Created June 2, 2022 at 3:40 PM
Updated June 24, 2024 at 6:37 AM
Resolved December 28, 2023 at 7:08 AM