lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <>
Subject Re: operator precedence and confusing result
Date Mon, 16 Mar 2009 21:19:01 GMT

The best thing to do is to use Luke to explain how the query parser is
reading your query.

See or for a
download and  web start link.

And, no, the proximity query should not match if both words are not
present.  But users are notoriously unreliable witnesses relative to this
sort of thing.

On Mon, Mar 16, 2009 at 12:55 PM, Jenny Brown <> wrote:

> I often have users performing a search like:
> "music arts"~10 OR "band festival" OR "rock concert"
> and then reporting back to me that they'll see results containing just
> the word band, or just the word concert, that don't match an entire
> phrase.  Am I misunderstanding phrase search here?  Is the proximity
> search changing the behavior of the whole query?

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