Re: DEFAULT_OPERATOR_AND globally ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Helmut Jarausch schrieb: > I know how to set DEFAULT_OPERATOR_AND for an individual QueryParser > Objekt (after creation) > > Since I always want this to be set, is there a means to set a (global) > option such that any QueryParser

Re: DEFAULT_OPERATOR_AND globally ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Helmut Jarausch schrieb: Hi Helmut, > I know how to set DEFAULT_OPERATOR_AND for an individual QueryParser > Objekt (after creation) > > Since I always want this to be set, is there a means to set a (global) > option such that

Re: DEFAULT_OPERATOR_AND globally ?

On Wednesday 12 December 2007 03:34:08 Helmut Jarausch wrote: > Hi, > > I know how to set DEFAULT_OPERATOR_AND for an individual QueryParser > Objekt (after creation) > > Since I always want this to be set, is there a means to set a (global) > option such that any QueryP

DEFAULT_OPERATOR_AND globally ?

Hi, I know how to set DEFAULT_OPERATOR_AND for an individual QueryParser Objekt (after creation) Since I always want this to be set, is there a means to set a (global) option such that any QueryParser object has this default operator. Many thanks for a hint, Helmut Jarausch Lehrstuhl fuer

DEFAULT_OPERATOR_AND globally ?

Hi, I know how to set DEFAULT_OPERATOR_AND for an individual QueryParser Objekt (after creation) Since I always want this to be set, is there a means to set a (global) option such that any QueryParser object has this default operator. Many thanks for a hint, Helmut Jarausch Lehrstuhl fuer

Re: DEFAULT_OPERATOR_AND

ik -Original Message- From: Erik Hatcher [mailto:[EMAIL PROTECTED] Sent: Thursday, August 18, 2005 4:07 PM To: java-user@lucene.apache.org Subject: Re: DEFAULT_OPERATOR_AND On Aug 18, 2005, at 1:48 AM, Karthik N S wrote: Does this mean MultiFieldQueryParser will always have to use 

RE: DEFAULT_OPERATOR_AND

tent:blue +content:dial +content:watch returned 10+ hits Please can u give enlighten me with more some ideas With regards Karthik -Original Message- From: Erik Hatcher [mailto:[EMAIL PROTECTED] Sent: Thursday, August 18, 2005 4:07 PM To: java-user@lucene.apache.org Subject: Re: DEFAULT_OP

RE: DEFAULT_OPERATOR_AND

ooleanQuery. Andrew -Original Message- From: Karthik N S <[EMAIL PROTECTED]> Sent: Aug 18, 2005 12:48 AM To: java-user@lucene.apache.org Subject: RE: DEFAULT_OPERATOR_AND Hi Luceners.. Apologies... Does this mean MultiFieldQueryParser will always have to use '

Re: DEFAULT_OPERATOR_AND

On Aug 18, 2005, at 1:48 AM, Karthik N S wrote: Does this mean MultiFieldQueryParser will always have to use 'DEFAULT_OPERATOR_OR' instead of DEFAULT_OPERATOR_AND operations. Yup, that's what I said :) Is there any alternative in handling this processs ( other then

RE: DEFAULT_OPERATOR_AND

Hi Luceners.. Apologies... Does this mean MultiFieldQueryParser will always have to use 'DEFAULT_OPERATOR_OR' instead of DEFAULT_OPERATOR_AND operations. Is there any alternative in handling this processs ( other then API 'replaceAll(" ", " AND ")

Re: DEFAULT_OPERATOR_AND

On Aug 17, 2005, at 2:45 AM, Karthik N S wrote: Hi Lucener's Apologies.. I have seen forms using 'DEFAULT_OPERATOR_AND' with something like below > QueryParser parser = new QueryParser( "terms", analyzer); > parser.setOperator(QueryParser.

DEFAULT_OPERATOR_AND

  Hi  Lucener's Apologies.. I have seen forms using  'DEFAULT_OPERATOR_AND'  with  something like below > QueryParser parser = new QueryParser( "terms", analyzer);  > parser.setOperator(QueryParser.DEFAULT_OPERATOR_AND);  > query = parser.pars