Question

I’m wondering if there are any recommendations, best practises or top-tips for integrating a Lucene.NET based search into an ASP.NET MVC web application?

Things I’ve read (or think I’ve read) in various places include the following:

• One IndexWriter, many IndexReaders
• When the index is updated, reset/ re-initialise the IndexReaders

Are there any other useful tips or resources I should read before starting?

Thanks,
Kieron

Answer 1

Here are my tips (in no particular order):

• Choose the most appropriate locking mechanism.
• Use the SetRAMBufferSizeMB to reduce the disk I/O overhead when writing the index.
• Don’t over use the SetMaxBufferedDocs property.
• Use the Search hits (TopDocs and ScoreDoc[]) object to retrieve the index search results.
• Index writing is an expensive operation, so use it sparingly.
• Know the data that you will be indexing as some data types (I.E., dates) can be difficult to search on if they are not stored consistently.

A few gotchas from one of my previous projects were:

• I had to use the BooleanQuery to do a traditional AND operation for searching multiple fields.
• There is no UPDATE functionality within Lucene so a document needs to be deleted and re-added.
• You can’t sort / OrderBy on a tokenized field.

I would suggest looking at the source code for RavenDb as it is built on top of Lucene and uses a number of best practices.