Merge InnoDB test cases from MySQL 5.7 (MDEV-13626)

[MDEV-14258] fix innodb_fts.compatibility.test Created: 2017-11-02  Updated: 2023-11-08  Resolved: 2023-11-08

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Technical task Priority: Major
Reporter: Alice Sherepa Assignee: Marko Mäkelä
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

https://github.com/MariaDB/server/tree/bb-10.2-alice/mysql-test/suite/innodb_fts/t/compatibility.test
test from mysql 5.7.

CURRENT_TEST: innodb_fts.compatibility
mysqltest: At line 96: query 'SELECT * FROM t1 WHERE MATCH(a, b) AGAINST ('TEST2')' succeeded - should have failed with errno 1764...
 
The result from queries just before the failure was:
< snip >
FTS_0	test/FTS_AUX_INDEX_6
FTS_0	test/FTS_AUX_BEING_DELETED
FTS_0	test/FTS_AUX_BEING_DELETED_CACHE
FTS_0	test/FTS_AUX_CONFIG
FTS_0	test/FTS_AUX_DELETED
FTS_0	test/FTS_AUX_DELETED_CACHE
DROP TABLE t1;
# Non windows aux table flag failure and rebuild the corrupted index.
call mtr.add_suppression("\\[Warning\\] InnoDB: Parent table of FTS auxiliary table .* not found.");
call mtr.add_suppression("\\[Warning\\] InnoDB: Setting aux table .* to hex format failed.");
call mtr.add_suppression("\\[ERROR\\] InnoDB: Index .* of table .* is corrupted");
SET GLOBAL DEBUG_DBUG='+d,innodb_test_wrong_fts_aux_table_name';
CREATE TABLE t1(a TEXT, b TEXT, c TEXT, FULLTEXT `AB` (a, b), FULLTEXT `C1` (c));
INSERT INTO t1 VALUES('TEST1', 'TEST2', 'TEXT3');
INSERT INTO t1 VALUES('TEXT1', 'TEXT2', 'TEXT5');
SELECT * FROM t1 WHERE MATCH(a, b) AGAINST ('TEST2');
a	b	c
SELECT * FROM t1 WHERE MATCH(c) AGAINST ('TEXT5');
a	b	c
SELECT * FROM t1 WHERE MATCH(a, b) AGAINST ('TEST2');

also similar to compatibility_win.test https://github.com/MariaDB/server/blob/mdev-13626/mysql-test/suite/innodb_fts/t/compatibility_win.test



 Comments   
Comment by Marko Mäkelä [ 2023-11-08 ]

The purpose of this test was to test compatibility with a bug that was specific to the Microsoft Windows version of MySQL, because an incorrect printf pattern was being used to generate the internal table names for fulltext indexes. We concluded in MDEV-18867 that the only GA release of MariaDB that this bug ever affected was the Microsoft Windows build of 10.0.10.

Generated at Thu Feb 08 08:12:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.