lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wolf Siberski <>
Subject BooleanQuery Semantics (was: [Bug 31841] - [PATCH] MultiSearcher...)
Date Wed, 22 Jun 2005 09:05:16 GMT wrote:
> ------- Additional Comments From  2005-06-21 23:08 -------
> There might be one corner case that your change in equals doesn't get right 
> (not tested): a query "a b a" (i.e. one clause occuring twice -- doesn't make 
> much sense, but has an influence on the result order) would equal "a b b", 
> wouldn't it? Is that a problem?  

Maybe naively, I assumed that BooleanQuery just follows the classical
boolean logic approach. Then "a b a" and "a b b" should yield exactly
the same result. On the other hand, I can follow your reasoning that
the current implementation will compute different scores for these queries.

So the question is: Which one is the *intended* semantics of BooleanQuery?

Depending on the answer, either my change to BooleanQuery.equals() shouldn't
be applied, or BooleanQuery needs to be fixed in another way, e.g. by
removing duplicate clauses in BooleanQuery.rewrite().


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

View raw message