]
Sent: Monday, October 27, 2008 10:43 AM
To: java-user@lucene.apache.org
Subject: Re: Lucene 2.2.0 Strange QueryParser behavior
OR is both a stopword and a reserved word In this case you
*probably* are getting hit by it being a stopword.
Changing your analyzer to not use stopwords is probably
OR is both a stopword and a reserved word In this
case you *probably* are getting hit by it being a stopword.
Changing your analyzer to not use stopwords is probably
the way to go, but beware that you should probably use the
same analyzer at index AND query time.
If you're using StandardAnalyz
Hi all,
I'm hoping this is an easy question. I have a Lucene index that contains
names and states, and I'm having an issue when the state is Oregon,
specifically OR. Below is an example of the query I pass in and the
query string that QueryParser builds below it.
This works for every state except
