Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Date: Fri, 05 Dec 2003 15:34:38 -0500
From: "Pleasant, Tracy" <tracy.pleasant@lmco.com>
Subject: RE: Returning one result
To: Lucene Users List <lucene-user@jakarta.apache.org>
Message-id: <1B76D3F17F4BE44283AD3C1C92AB590B01D1E7A1@EMSS04M14.us.lmco.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: Returning one result
Thread-Index: AcO7bxrUZWj0M2KkRXuNgEfoIvuzzgAAApQw
content-class: urn:content-classes:message

Yes it is in the list of arrays that I want searched.

-----Original Message-----
From: Dror Matalon [mailto:dror@zapatec.com]
Sent: Friday, December 05, 2003 3:32 PM
To: Lucene Users List
Subject: Re: Returning one result


On Fri, Dec 05, 2003 at 03:14:08PM -0500, Pleasant, Tracy wrote:
> What do you mean 'add' in MultiFieldQueryParser?  I am using all the
> fields 

Sorry, that was wrong. What I meant to say is are you adding the field
to the array of fields that need to be searched? 

You need to use a MultiFieldQueryParser and pass it the array of fields
that you want searched.

Dror

> 
> When I index it does 
> 
>  add (Field.Keyword(..,..))
> 
> 
> But I don't want the user to have to type ID:<ID NUMBER> It would be
> nice to just type ID Number. On your site if you just put: 11183 in
the
> search box there are no results. 
> 
> well, right now I'll just do it as text and query that field for the
id
> # to display the document.  It can't hurt, right? :)  Unless the
Keyword
> is a better way
> 
> 
> 
> -----Original Message-----
> From: Dror Matalon [mailto:dror@zapatec.com]
> Sent: Friday, December 05, 2003 3:06 PM
> To: Lucene Users List
> Subject: Re: Returning one result
> 
> 
> On Fri, Dec 05, 2003 at 02:45:34PM -0500, Pleasant, Tracy wrote:
> > Maybe we are having some communication issues. 
> > 
> > At any rate, I did index it as a KEYWORD and when displaying used
the
> > TermQuery.
> > 
> > The only problem with this though is by storing the ID (i.e. AR345)
as
> a
> > Keyword, if I search for AR345 no results are returned when I use
the
> > MultiFieldQueryParser .
> > 
> > *sigh* *arg*
> 
> OK. 
> 
> Go to http://www.fastbuzz.com/search/index.jsp and type "lucene"
without
> the quotes  and hit search. You get results from different
channels/rss
> feeds.
> 
> Now type "lucene channel:11183" without the quotes and hit search. You
> get results only from Java-Channel. 
> 
> We're inserting the field channel as a keyword, and it does what I
> understand you want to use AR345.
> 
> I would guess that in MultiFieldQueryParser you are not doing an add()
> of the field for AR345 which is why the search fails. 
> 
> Regards,
> 
> Dror
> 
> 
> > 
> > 
> > 
> > -----Original Message-----
> > From: Erik Hatcher [mailto:erik@ehatchersolutions.com]
> > Sent: Friday, December 05, 2003 2:13 PM
> > To: Lucene Users List
> > Subject: Re: Returning one result
> > 
> > 
> > On Friday, December 5, 2003, at 01:25  PM, Pleasant, Tracy wrote:
> > > Say ID is Ar3453 .. well the user may want to search for Ar3453,
so
> in
> > > order for it to be searchable then it would have to be indexed and
> not
> > 
> > > a
> > > keyword.
> > 
> > *arg* - we're having a serious communication issue here.  My advice
to
> 
> > you is to actually write some simple tests (test-driven learning
using
> 
> > JUnit is a wonderful way to experiement with Lucene, especially
thanks
> 
> > to the RAMDirectory).  Please refer to my articles at java.net as
well
> 
> > as the other great Lucene articles out there.
> > 
> > Let me try again.... a Field.Keyword *IS* indexed!  Even Lucene's 
> > javadocs say this for this method:
> > 
> >    /** Constructs a String-valued Field that is not tokenized, but
is 
> >  >>>indexed<<<
> >      and stored.  Useful for non-text fields, e.g. date or url.  */
> > 
> > [I added the emphasis there]
> > 
> > 
> > > So after using
> > > TermQuery query = new TermQuery(new Term("id", term));
> > >
> > > How would I return the other fields in the document?
> > >
> > > For instance to display a record it would get the record with the
id
> #
> > > and then display the title, contents, etc.
> > 
> > Umm.... you'd use *exactly* the same way as if you had used 
> > QueryParser.  QueryParser would create a TermQuery for you, in fact,

> > except it would analyze your text first, which is what you want to 
> > avoid, right?
> > 
> > Hits.doc(n) gives you back a Document.  And then 
> > Document.get("fieldName") gives you back the fields (as long as you
> >>> 
> > stored <<< them in the index too).
> > 
> > Again, please attempt some of these things in code.  It is a trivial

> > matter to index and search using RAMDirectory and experiment with 
> > TermQuery, QueryParser, Analyzers, etc.
> > 
> > 	Erik
> > 
> > 
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> > 
> > 
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> > 
> 
> -- 
> Dror Matalon
> Zapatec Inc 
> 1700 MLK Way
> Berkeley, CA 94709
> http://www.fastbuzz.com
> http://www.zapatec.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> 

-- 
Dror Matalon
Zapatec Inc 
1700 MLK Way
Berkeley, CA 94709
http://www.fastbuzz.com
http://www.zapatec.com

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


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