Bug #92118 innodb_ft_enable_stopword is wrongly described as "GLOBAL" scope in Docs

• Submitted: 22 Aug 2018 8:20
• Modified: 28 Aug 2018 17:53
• Reporter: Tsubasa Tanaka (OCA)
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 8.0, 5.7, 5.6,
• OS: Any
• CPU Architecture: Any

[22 Aug 2018 8:20] Tsubasa Tanaka

Description:
Docs say innodb_ft_enable_stopword has only "Global" scope, but actually innodb_ft_enable_stopword has both of "Global" and "Session".

```
mysql80 22> SELECT @@session.innodb_ft_enable_stopword, @@global.innodb_ft_enable_stopword;
+-------------------------------------+------------------------------------+
| @@session.innodb_ft_enable_stopword | @@global.innodb_ft_enable_stopword |
+-------------------------------------+------------------------------------+
|                                   1 |                                  1 |
+-------------------------------------+------------------------------------+
1 row in set (0.01 sec)
```

ft_enable_stopword defined as "MYSQL_THDVAR_BOOL", not "MYSQL_SYSVAR_BOOL". 
So this is documentation-issue, I think.

https://github.com/mysql/mysql-server/blob/mysql-8.0.12/storage/innobase/handler/ha_innodb...

How to repeat:
See docs.

https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_ft_enable_sto...

https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_ft_enable_sto...

https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_ft_enable_sto...

https://dev.mysql.com/doc/refman/5.6/ja/innodb-parameters.html#sysvar_innodb_ft_enable_sto...

Suggested fix:
Fix "scope" of innodb_ft_enable_stopword to "Global, Session" in Docs.

[22 Aug 2018 8:21] Tsubasa Tanaka

I think Bug#91567 is caused this...

[22 Aug 2018 8:29] MySQL Verification Team

Thank you for the bug report.

[28 Aug 2018 17:53] Daniel Price

Posted by developer:
 
The referenced documentation was updated. Changes should appear online shortly. 
Thank you for the bug report.