Bug #116707 when innodb_optimize_fulltext_only=ON, optimize table return OK always
Submitted: 19 Nov 2024 11:49 Modified: 19 Nov 2024 12:20
Reporter: Huaxiong Song (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: DDL Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[19 Nov 2024 11:49] Huaxiong Song 
Description:
As stated in the title, when innodb_optimize_fulltext_only=ON, when optimizing a table containing a full-text index, success is always returned regardless of success or failure.

How to repeat:
CREATE TABLE t1 (a VARCHAR(200), b TEXT, FULLTEXT (a,b));

SET GLOBAL innodb_optimize_fulltext_only=ON;

--echo Should be successful.
OPTIMIZE TABLE t1;

SET DEBUG = '+d, fts_instrument_sync_interrupted';
--echo Should be failed, but return OK.
OPTIMIZE TABLE t1;

SET GLOBAL innodb_optimize_fulltext_only=OFF;
SET DEBUG = '-d, fts_instrument_sync_interrupted';
DROP TABLE t1;

Suggested fix:
Check the retval of `fts_sync_table` and `fts_optimize_table`.
[19 Nov 2024 11:52] Huaxiong Song 
Bugfix of bug#116707

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: bug#116707.patch (application/octet-stream, text), 2.19 KiB.
[19 Nov 2024 12:20] MySQL Verification Team 
Hello Huaxiong,

Thank you for the report and contribution.

regards,
Umesh