lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: back compat is good
Date Wed, 10 Jun 2009 19:15:09 GMT
On Wed, Jun 10, 2009 at 2:23 PM, Yonik Seeley<> wrote:

>> Well... Lucene still seems to be experiencing strong adoption/growth,
>> eg combined user+dev email traffic:
> I think that includes all Lucene sub-projects (Solr, Tika, Mahout,
> Nutch, Droids, etc).

Woops you're right.  java-user alone looks to have flattened out
recently... though usage of eg Solr is also usage of Lucene:

What I'd really love to see is "how many cumulative searches have
been done by Lucene, everywhere" as a function of time...

>> And it pains me when our back compat policy forces us to sacrifice new
>> users' experience (not being to change default settings; not being
>> able to fix bugs in analyzers; etc).
> As far as default settings, it seems like it can be mostly fixed with
> documentation (i.e. recommended settings for maximum performance).
> That seems like a very small burden for people writing new
> applications with Lucene anyway (compare to the cost of writing the
> whole application).  On the other hand, existing users may be
> essentially "done" with the Lucene development in their project, and
> want to upgrade for bug fixes, performance increases, and maybe to
> incrementally add new features.

I think we need to do both.  We should doc things like "use a big RAM
buffer", "turn off CFS", "use an SSD", "use threads", etc.

But for things like "open a readOnly reader", "turn on the acronym fix
in StandardAnalyzer", "use BooleanScorer not BooleanScorer2", "don't
discard positions in StopFilter", "use NIOFSDirectory not
FSDirectory", "turn off scoring when sorting by field", we should fix
Lucene to do those by default.

I'd like for Lucene to make a good first impression.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message