Bug #19583 | Fulltext boolean mode search stopword issue | ||
---|---|---|---|
Submitted: | 6 May 2006 16:05 | Modified: | 4 Aug 2006 9:32 |
Reporter: | Jonathan Fiene | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1.14 | OS: | Linux (Linux) |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
[6 May 2006 16:05]
Jonathan Fiene
[11 May 2006 17:11]
Valeriy Kravchuk
Thank you for a problem report. Please, send exact CREATE TABLE statement and some test data to demonstrate the bug. Please, check also on newer version, 4.1.19.
[11 Jun 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[4 Aug 2006 9:32]
Sergey Vojtovich
For now '+one*' means at least one non-stopword that starts with 'one' must be present in document. As a workaround you can either remove this word from stopwords or switch stopwords feature off. Unfortunately there is no way to do it on table-by-table basis. There is possible way to retreive stopwords. MySQL has ft_stopword_file server variable. If it's value is built-in you can find array of stopwords in myisam/ft_static.c, otherwise you can read stopwords file. This problem is to be fixed in future and will be tracked by WL#2573.