We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The default full-text stopword list is quite large:
https://dev.mysql.com/doc/refman/8.0/en/fulltext-stopwords.html#fulltext-stopwords-stopwords-for-myisam-search-indexes
Unfortunately, it contains many words which are significant in the identification of music-related material.
I propose we override the default stopword list with the much smaller stopword list that is used by default for InnoDB search indexes:
https://dev.mysql.com/doc/refman/8.0/en/fulltext-stopwords.html#fulltext-stopwords-stopwords-for-innodb-search-indexes
Given that zookeeper is not a massive database, the overhead to index the extra words should not present a storage or performance problem.
The text was updated successfully, but these errors were encountered:
The kzsu production configuration has been updated and the indexes rebuilt.
The list of stopwords in kzsu prod as of 2020-07-31
In addition, the minimum full text word length has been reduced from 4 characters to 3.
Sorry, something went wrong.
No branches or pull requests
The default full-text stopword list is quite large:
https://dev.mysql.com/doc/refman/8.0/en/fulltext-stopwords.html#fulltext-stopwords-stopwords-for-myisam-search-indexes
Unfortunately, it contains many words which are significant in the identification of music-related material.
I propose we override the default stopword list with the much smaller stopword list that is used by default for InnoDB search indexes:
https://dev.mysql.com/doc/refman/8.0/en/fulltext-stopwords.html#fulltext-stopwords-stopwords-for-innodb-search-indexes
Given that zookeeper is not a massive database, the overhead to index the extra words should not present a storage or performance problem.
The text was updated successfully, but these errors were encountered: