MySQL Forums
Forum List  »  Docs

Need authoritative reference re safety of changing ft_min_word_length
Posted by: Alex Matulich
Date: July 06, 2006 03:22PM

The Fine-Tuning MySQL documentation needs clarification on consequences of resetting the system variable 'ft_min_word_len'.

I need to set ft_min_word_length=3, so that my users can perform boolean fulltext searches for words of three characters instead of four. However, I share the MySQL server with other customers of my ISP. My ISP's administrator is willing to change this system variable, provided I can show him an authoritative source that says doing so won't break anything if other customers don't rebuild their FULLTEXT indexes.

The description on http://dev.mysql.com/doc/refman/5.1/en/fulltext-fine-tuning.html contains no warnings; the text only implies that setting ft_min_word_len=3 will have no effect until you rebuild your FULLTEXT indexes (which will continue to work as they did before).

The following quote from my admin's latest email explains his problem:
Quote

Can you find any authoritative source that actually says that the only consequence is that text searches won't find any 3-character words because the fulltext index won't contain them until it's rebuilt? The MYSQL manual doesn't clearly say this, and it does say that "you must rebuild your fulltext index."

There are quite a few other MySQL databases on the server, many of them automatically created when installatron is used, and I have no idea if any of them use fulltext searches. I can't afford the risk of any of them breaking. So all I need is some authoritative source that says that existing databases will not be affected."

Anybody know of an authoritative source? If not, can a clarifying statement be added to the documentation that describes the consequences of changing ft_min_word_len without rebuilding the FULLTEXT indexes?

-Alex

Options: ReplyQuote


Subject
Views
Written By
Posted
Need authoritative reference re safety of changing ft_min_word_length
6715
July 06, 2006 03:22PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.