lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Unexpected results searching for phrase with stop words
Date Thu, 12 Nov 2009 20:15:46 GMT
Yes, you're doing something wrong <G>. What, you may ask?
Well, it's kind of hard to say without knowing what analyzers
you use at index AND query time and what the query you're
submitting looks like...

But the very first thing I'd try is to get a copy of Luke and peek at your
index to see if what you *think* is in there actually is.

Then, I'd run some queries through Luke (you can choose various
analyzers) and see what the query looks like after it's parsed.

In parallel, try query.toString() to see what the parsed query looks like,
might surprise you.


On Thu, Nov 12, 2009 at 3:00 PM, Simon Wistow <> wrote:

> I have a document with the title "Here, there be dragons" and a body.
> When I search for
> Here, there be dragons
> (no quotes)
> with a title boost of 2.0 and a body boost of 0.8
> I get the document as the first hit which is what I'd expect.
> However, if change the query to
> "Here, there be dragons"
> (with quotes)
> then I don't get the document at all. Which is not what I'd expect.
> I've tried modifying the phrase slop but still don't get any results
> back.
> Am I doing something wrong? I suspect it's something to do with the
> number of stop words in the query. Do I have to have an untokenized copy
> of the title field lying around to search on?
> Thanks,
> Simon
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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