[MDEV-33180] Table truncate fails for InnoDB table with FULLTEXT KEY when innodb_ft_user_stopword_table is set Created: 2024-01-04 Updated: 2024-01-04 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Full-text Search, Storage Engine - InnoDB |
| Affects Version/s: | 10.6.14, 10.11.5, 10.11.6 |
| Fix Version/s: | 10.6, 10.11 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Marco Kropivsek | Assignee: | Thirunarayanan Balathandayuthapani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
MS Windows 10 Enterprise 10.0.19045 Server: Docker Desktop 4.25.2 (129061) The issue also occurs on Ubuntu 20.04.6 LTS / MariaDB 10.6.14. |
||
| Attachments: |
|
| Description |
|
We have build a docker image based on mariadb:10.11.5-jammy / mariadb:10.11.6-jammy. This image has been slightly modified so that a FULLTEXT KEY uses non-default stopword data that is available in the table oms_stopword_db.oms_ft_default_stopword. A TRUNCATE TABLE command on a table that has a FULLTEXT KEY, crashes the database. The following steps can be used to reproduce the error (the necessary files have been attached): 1) Build the MariaDB image (from the folder that contains the Dockerfile / other necessary files): 2) Start the MariaDB image (please ignore the MARIADB_USER/MARIADB_PASSWORD; this user is not used): 3) Connect to the acm-database image: 4) Conect to the MariaDB with the mysql client: 5) Check that the stopword table setting: 6) Create the database: 7) Switch to the test_db: 8) Create the test_table: 9) Truncate the table: 10) Server crash. |