将ft_stopword_file设置为默认（内置）而无需重新启动mysql
我需要通过更改ft_stopword_file而无需重新启动服务器来测试某些内容。我知道设置全局有效更改全局变量，直到下一个重新启动为止。测试后，我想将其返回其默认值，以防万一它打破某些内容。
问题是：如果我正确理解，ft_stopword_file在完全不设置时仅重置为默认值（其内置单词集）（换句话说：no ft_stop_word_file在my.cnf中）。
有没有办法设置它（无论是设置global还是任何其他命令）可以再次使用内置单词集，而无需重新启动服务器？
I need to test something by changing the ft_stopword_file without restarting the server. I know that SET GLOBAL works to change global variables until the next restart. After testing, I want to return it to its default value just in case it breaks something.
The problem is: if I understood correctly, ft_stopword_file only resets back to its default value (its built-in word set) when being completely unset (in other words: no ft_stop_word_file in my.cnf).
Is there a way to set it (be it with SET GLOBAL or any other command) to use the built-in word set again without needing to restart the server?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
是，否。
不，没有。
但是您可以将其设置为您选择的自定义列表，因此可以与内置单词集相同（您可以在 fine Source ）。仅当变量值恰好是“（内置）”时，您才需要执行此操作。
即使将其从主列表设置为相同列表，您也必须运行
修理表您的快速才能消化它。Yes and no.
No, there isn't.
But you can set it to a custom list of your choice, which can therefore be identical to the built-in word set (you find this in the fine sources). You need to do this only if the variable value happens to be "(built-in)".
Even if you set it from the main list to the identical list, you will have to run a
REPAIR TABLE yourtable QUICKto have it digested.什么是最终目标？这些都足够吗？
计划A：
Myisam？它将很快消失。也许您应该在InnoDB中设置桌子。 InnoDB的所有设置都与Myisam分开。全文的两个实现之间存在许多细微的差异。停车文件只是其中之一。
计划B：
旋转单独的服务器（或在同一服务器上实例）。设置您需要的任何东西。使用MySQLDUMP（或类似）将数据从一个实例移至另一个实例，并具有适当的参数。如果合适，请使新实例较小，并在mysqldump上使用“ Where”参数来限制复制的数据量。
What is the ultimate goal? Would either of these suffice?
Plan A:
MyISAM? It will be going away soon. Perhaps you should set up the table in InnoDB. All the settings for InnoDB are separate from those of MyISAM. There are many subtle differences between the two implementations of Fulltext; the stopword file is just one of them.
Plan B:
Spin up a separate server (or instance on the same server). Set whatever you need it it. Move data from one instance to the other using mysqldump (or similar) with appropriate arguments. If appropriate, make the new instance smaller and use a "where" argument on mysqldump to limit the amount of data copied over.