Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Tatu Saloranta <tatu@hypermall.net>
Reply-To: tatu@hypermall.net
Organization: Linux-users missalie
To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Subject: Re: About Query...
Date: Mon, 17 Mar 2003 08:02:55 -0700
User-Agent: KMail/1.4.3
References: <63DF0F1EBF89D21191B30090271F42793F5DF6@asterix.intrapeople.lu>
In-Reply-To: <63DF0F1EBF89D21191B30090271F42793F5DF6@asterix.intrapeople.lu>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200303170802.55941.tatu@hypermall.net>

On Monday 17 March 2003 04:32, Pierre Lacchini wrote:
> sorry for my poor english...
>
> Well if i perform a Multiple Fields query... Why do I have to specify the
> name of the field in the parse method ?
> Because i'm using 2 field in the query...

Query parser has to know which field term should be matched against by 
default, if user does not explicitly specify field, and that field is passed 
to query constructor. At this point actual query is not known; it's passed 
with parse methods, and parser can be used multiple times (although it's not 
re-entrant).

Method you are calling is a convenience method that just creates a new parser 
for this particular query, then calls non-static parse method.

I _think_ you can just pass null (or dummy field name) in your case if you are 
absolutely sure fields for all terms are defined in query.

-+ Tatu +-


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org