Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <20090728141350.39OT6.484940.imail@eastrmwml34>
Date: Tue, 28 Jul 2009 14:13:50 -0400
From: <ohaya@cox.net>
To: java-user@lucene.apache.org
Subject: Re: New to Lucene - some questions about demo
In-Reply-To: <4A6F30FE.80109@informatics.jax.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sensitivity: Normal

Matthew,

Ok, thanks for the clarifications.

When I have some quiet time, I'll try to re-do the tests I did earlier and post back if any questions.

Thanks again,
Jim

---- Matthew Hall <mhall@informatics.jax.org> wrote: 
> Oh.. no.
> 
> If you specifically include a fieldname: blah in your clause, you don't 
> need a MultiFieldQueryParser.
> 
> The purpose of the MFQP is to turn queries like this "blah" 
> automatically into this "field1: blah" AND "field2: blah" AND "field3: 
> blah" (Or OR if you set it up properly)
> 
> When you setup the MFQP you specify what fields you want to have this 
> behavior apply to, and can even give each field its own specific analyzer.
> 
> So if in your index you have multiple fields, each of which was created 
> with a different analyzer, you could search these effortlessly in your 
> webapp using the MFQP.
> 
> (If for example you have an exact_contents and a contents field, one 
> where punctuation and capitalization matters, one where it does not)
> 
> Hope that clears things up for you.
> 
> Matt


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