You still haven't provided the data. Here's what Mr. Hatcher needs you to do.
Provide a very short program that demonstrates this. It should parse a query and print out the parsed query using ToString. For instance, are you lowercasing the query before parsing? In which case or is not treated as an operator, but a term. We can keep going back and forth only to discover that you are not providing complete information. Or we're assuming something you aren't. or.... the 10,000 ways we can talk past each other without providing crucial information. So, please provide a short, self-contained program that demonstrates the problem and I'm sure Mr. Hatcher will provide an answer in a trice. I'm going to guess that you won't be able to do this, and in the process you'll discover that you did something like... instantiated a new QueryParser and didn't set the default operator as you think. Or lowercased the query. Or set the default operator on a different QueryParser than you actually used. Or...... Best Erick On 2/19/07, Karimi-Tabatabaie Jamal <[EMAIL PROTECTED]> wrote:
Exactly. That means that last query "Lucene OR Query" must be parsed correct to "Lucene query" with the OR operator while default operator is set to AND. Right? But in my implementation with default operator set to AND the query 'Hare OR Tortoise' is parsed to 'Hare AND Tortoise'! Regards, Jamal -----Ursprüngliche Nachricht----- Von: Erick Erickson [mailto:[EMAIL PROTECTED] Gesendet: Montag, 19. Februar 2007 14:45 An: java-user@lucene.apache.org Betreff: Re: QueryParser explicit and implicit search operator <<<How else would you explain the 316 search results, when the results for each single queries "Lucene" and "Query" is lesser than 316?>>> Because some documents contain "Lucene" but not "Query" and vice-versa. These results look perfectly reasonable to me too. The default operator is AND, which is why queries 3 and 4 return the same results. When you query on "Query" you get some number of documents (109 to be exact) that ALSO contain "Lucene". The reverse is also true, when you query "Lucene", 109 of those documents also contain "Query". So, if you subtract 109 (look familiar?) from the sum of the individual queries for Lucene and Query, you get 316 (155 + 270 - 109) which is exactly what you get from "Lucene OR Query". All fine from my perspective. Best Erick On 2/19/07, Karimi-Tabatabaie Jamal <[EMAIL PROTECTED]> wrote: > > Hello Erik, > > You are right for a little complex query. I tested the following queries > > serach at lucenebool.com with query "Query" 155 results > serach at lucenebool.com with query "Lucene" 270 results > serach at lucenebool.com with query "Query AND Lucene" 109 results > serach at lucenebool.com with query "Query Lucene" 109 results > serach at lucenebool.com with query "Query OR Lucene" 316 results > > and came to the guess that it seems to be fixed for a query like "X OR Y"! > How else would you explain the 316 search results, when the results for each > single queries "Lucene" and "Query" is lesser than 316? > > Jamal > > -----Ursprüngliche Nachricht----- > Von: Erik Hatcher [mailto:[EMAIL PROTECTED] > Gesendet: Samstag, 17. Februar 2007 06:27 > An: java-user@lucene.apache.org > Betreff: Re: QueryParser explicit and implicit search operator > > > On Feb 16, 2007, at 1:53 PM, Karimi-Tabatabaie Jamal wrote: > > For my problem there seems to exist a lucence Bug > > (http://issues.apache.org/jira/browse/LUCENE-167) but also it seems > > that > > it's solved in the Lucene integration on site http:// > > www.lucenebook.com. > > Where do you see the problem solved at lucenebook.com? The "Query > parsed to:" for this query <http://www.lucenebook.com/search? > query=aaaaa+AND+bbbbb+OR+ccccc+AND+ddddd> is > > Query parsed to: +aaaaa bbbbb +ccccc +ddddd > > The OR caused the "bbbbb" term to not be required, yet all other > terms are required. > > Erik > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
