lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <mar...@rectangular.com>
Subject Re: Lucene's default settings & back compatibility
Date Wed, 20 May 2009 15:06:13 GMT
On Wed, May 20, 2009 at 05:57:49PM +0400, Earwin Burrfoot wrote:

> > What happens when two libraries loaded in the same VM have Lucene as a
> > dependency and set actsAsVersion to conflicting numbers?

> Exactly what happens when you call BooleanQuery.setMaxClauseCount(n)
> from two libraries.
> Last one wins.

Yeesh, that's evil.  :(

It will be sweet, sweet justice if one of your own projects gets infected by
the kind of action-at-a-distance bug you're so blithely unconcerned about.

http://en.wikipedia.org/wiki/Action_at_a_distance_(computer_science)

That was supposed to be a rhetorical question.  To be clear, I consider the
idea of a settable global variable determining library behavior completely
unacceptable.  Changing class load order somewhere in your code shouldn't do
things like change search results (because Stopfilters are applied differently
depending on who "won").

Marvin Humphrey


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message