lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ChadDavis <chadmichaelda...@gmail.com>
Subject Re: lucene 1.4 booleanquery
Date Fri, 10 Oct 2008 17:14:38 GMT
So, I put add a query in the "should" fashion, it will return all things
matching that query, but they won't rank as high as required matches?

On Thu, Oct 9, 2008 at 6:26 PM, Chris Hostetter <hossman_lucene@fucit.org>wrote:

>
> : > Why would you submit a query with both of the booleans set to false?
> : >  What does this mean, functionally.  Use cases?
> :
> : There are no use cases, as it doesn't make sense. That's why the API is
> : different now and only allows MUST, MUST_NOT, and SHOULD.
>
> Actually setting both to "false" is valid -- that's the SHOULD use case.
> setting them both to "true" is not valid.
>
> ASs Lucene is not a strict Boolean Matching system, BooleanQuery doesn't
> apply strick boolean logic opperators.  if something is require it *must*
> match.  if something is prohibited it *must not* match.  if something is
> neither required nor prohibited then in *should* match ... the more
> "should" clauses that math, the better the score.
>
>
> -Hoss
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message