Skip to main content

Enterprise Java Community: I Love Lucene

Popularity Report

Total Popularity Score: 0

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Rank

Bookmark History

Saved by 6 people (-1 private), first by anonymouse user on 2006-10-08


Public Sticky notes

This cast study discusses how TheServerSide built an infrastructure that allows us to index, and search our different content using Lucene.

Highlighted by kenyth

You will also see a main(..) method. We created this to allow for a command line program to kick off a build process.

Highlighted by kenyth

We created a simple Java representation of this data, SearchContentHolder,

Highlighted by kenyth

create a fairly generic set of fields

Highlighted by kenyth

Highlighted by kenyth

have the concept of incremental indexing, as well as a full indexing from scratch. To take care of this we have an incrementalDays variable which is configured for the index process. If this value is set to 0 or less, then do a full index.

Highlighted by kenyth

possessing content that lives in different sources.

Highlighted by kenyth

this field NOT only the body of a thread message, but rather a concatenation of the title of the message, the owner of the message, and then finally the message contents itself. You could try to use Boolean queries to make sure that a search finds a good match, but we found it a LOT simpler to put in a cheeky concatenation!

Highlighted by kenyth

The date boost has been really important for us.

Highlighted by kenyth

There have been settings in both the indexing process, and search process, that were crying out for abstraction. Where should we put the index location, the category lists, the boost values, and register the index sources? We didn’t want to have this in code, and since the configuration was hierarchical we resorted to using XML.

Highlighted by kenyth