On Tue, May 19, 2009 at 6:47 AM, DM Smith <dmsmith...@gmail.com> wrote:
> It is common in my application, a Bible program, that indexes each verse > (think of a verse as a numbered sentence) as a separate document. We index > everything, including words that are typically stop words as those might be > important to our end users. Besides this, the top 280 word roots represent > 90% of the occurrences. > And on searches, we return everything in book order, unless the user wants > to score the result. In that case, we return a small, user configurable > amount of hits ordered by score. The ability to turn off scoring when sorting by field, new in 2.9, should be a good performance boost for your use case (if performance is important). > And we are using Lucene out of the box for the most part. We've deviated > only to incrementally solve performance problems. Right, my impression is most people will stick w/ Lucene's defaults, incrementally changing only limited settings they come across, which is why selecting good defaults is vital to Lucene's growth/adoption (new users especially simply start w/ our defaults). But we can't pick good defaults when we're so heavily bound by back-compat. Which is why I find the Settings approach so appealing :) Suddenly, on all improvements to Lucene, we have the freedom to change our defaults so a new user sees all such improvements. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
