MySQL Bugs: #12657: ft_min_word_len for every fulltext index

Bug #12657	ft_min_word_len for every fulltext index
Submitted:	18 Aug 2005 21:05	Modified:	28 Aug 2009 21:09
Reporter:	Andre Timmer	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: FULLTEXT search	Severity:	S4 (Feature request)
Version:	5	OS:	Any (Solaris, any)
Assigned to:		CPU Architecture:	Any

Description:
ft_min_word_len is set at database level and used for every fulltext index.

How to repeat:
create fulltext index.

Suggested fix:
Would like to set this per fulltext index.
This could also apply to ft_stopword_file.

I want to strongly agree with this suggestion.  There are many special cases where words shorter than 4 characters need to be included in a full-text index, such as acronyms, and in my case, descriptive words.  Such a special case might apply to one table or one index, but not others.  It's too inflexible to have this as a global server setting.

I also strongly support this feature request. In a shared hosting environment I have no access to the fulltext search fine tuning suggested in the manual - so all these settings should be at database, table, or index level, but not at server level. 
The 4 character minimum length and the stopword list can be a big problem in non-english environments - imagine a website on the geography and culture of Switzerland, where words such as "See" (lake), "Sent" (a village) or "Most" (apple juice) are ignored. 
Therefore - and because MySQL is most popular on shared hosting - I hope this will be scheduled for a version to come soon!

Pardon the "me too" message, but I strongly agree. In fact, I consider the min_word_len and the ignore list to be a language dependant optimizations which should only be solved at this level if it is highly customizable per index (see also bugreport #18695).

Is this still not fixed???   If not, I also strongly urge that it be.
For on of my applications, some example words we need to search are: "DNA", "RNA", "NGF" (nerve growth factor), "GLY" (Glycine) ...

Since each database and application is different it should be possible to customize this value for every database.  Many (or most) users of MySQL use shared hosting services which prevents them from having access to the server configuration.  These users need to be able to change the value for their own database!!!

Thank you for the reasonable feature request.

This feature request is still relevant 10 years later.  Ran into the same problem: shared hosting environment, "gps" doesn't show up in search results.  There are a good many use cases for which ft_min_word_len would be lovely to have configurable on a per-index basis.