AW: QueryParser explicit and implicit search operator

2007-02-19 Thread Karimi-Tabatabaie Jamal
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

AW: QueryParser explicit and implicit search operator

2007-02-19 Thread Karimi-Tabatabaie Jamal
ser 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,

AW: QueryParser explicit and implicit search operator

2007-02-19 Thread Karimi-Tabatabaie Jamal
ults 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 impli

QueryParser explicit and implicit search operator

2007-02-16 Thread Karimi-Tabatabaie Jamal
> hello, > > I have a problem with the QueryParser and the default search operator > AND. > > So let me please explain my problem in hope that you can help me. > > I have integrated the search engine in our CRM product. To make it > easier for the user we decided to set the default search oper