From 1edba03e3833cfd8bae84e6e04b50d3d8677c059 Mon Sep 17 00:00:00 2001 From: Elendil Date: Fri, 17 Jan 2025 14:53:20 +0800 Subject: [PATCH] Update concepts-server-parameters.md --- .../flexible-server/concepts-server-parameters.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/articles/mysql/flexible-server/concepts-server-parameters.md b/articles/mysql/flexible-server/concepts-server-parameters.md index effb361343..a53fce4c69 100644 --- a/articles/mysql/flexible-server/concepts-server-parameters.md +++ b/articles/mysql/flexible-server/concepts-server-parameters.md @@ -384,6 +384,19 @@ DO For servers with high availability configured, when failover occurs, it's possible that the `event_scheduler` server parameter is set to `OFF`. If this occurs, when the failover is complete, configure the parameter to set the value to `ON`. +### innodb_ft_user_stopword_table +`innodb_ft_user_stopword_table` is a server parameter in MySQL that specifies the name of the table containing custom stopwords for InnoDB Full-Text Search. The table must be in the same database as the full-text indexed table, and its first column must be of type `VARCHAR`. In Azure Database for MySQL - Flexible Server, the default setting of `sql_generate_invisible_primary_key=ON` causes all tables without an explicit primary key to automatically include an invisible primary key. This behavior conflicts with the requirements for `innodb_ft_user_stopword_table`, as the invisible primary key becomes the first column of the table, preventing it from functioning as intended during Full-Text Search. To resolve this issue, you must set `sql_generate_invisible_primary_key=OFF` in the same session before creating the custom stopword table. For example: + +```sql +SET sql_generate_invisible_primary_key = OFF; +CREATE TABLE my_stopword_table ( + stopword VARCHAR(50) NOT NULL +); +INSERT INTO my_stopword_table (stopword) VALUES ('and'), ('or'), ('the'); +``` + +This ensures the stopword table meets MySQL’s requirements and allows custom stopwords to work properly. + ## Nonmodifiable server parameters The **Server parameters** pane in the Azure portal shows both the modifiable and nonmodifiable server parameters. The nonmodifiable server parameters are unavailable. You can configure a nonmodifiable server parameter at the session level by using `init_connect` in the [Azure portal](./how-to-configure-server-parameters-portal.md#setting-non-modifiable-server-parameters) or the [Azure CLI](./how-to-configure-server-parameters-cli.md#setting-non-modifiable-server-parameters).