I know FogBugz uses the Lucene search engine and I know that it has a copy of the index in the database, and one on disk. How do these two interact?
|
2
2
|
|
|
|
|
2
|
By default FogBugz uses the search index stored in the database. It stores a clone of this index on disk because Lucene--the search engine software--only knows how to work with the filesystem. The main reason for the database index is so that a FogBugz setup which has a singular database but multiple web servers (such as On Demand) can share indexing data between the web servers without having to maintain separate indices. You can also move a FogBugz database to another server without having to do a full index rebuild. Having the index in two places can sometimes result in synchronization and/or performance issues. If you find that your searches aren't producing accurate results, you can regenerate the index files by deleting the data in the You can force FogBugz to only keep the filesystem index by following these instructions. This can speed your searches up significantly. To summarize:
|
||||||
|