lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Lea <>
Subject Re: New to Lucene - some questions about demo
Date Tue, 28 Jul 2009 13:14:04 GMT

Field.Index.NOT_ANALYZED means it will be stored as is i.e. "FooFoo"
in your example, and if you search for "foofoo" it won't match.  A
search for "FooFoo" would, assuming that your search terms are not
being lowercased.


On Tue, Jul 28, 2009 at 1:56 PM, Ohaya<> wrote:
> Hi,
> I'm just starting to work with Lucene, and I guess that I learn best by
> working with code, so I've started with the demos in the Lucene
> distribution.
> I got the and working, and also the
> luceneweb.war is deployed to Tomcat.
> I used to index some text files, and then used both the
> and the luceneweb web app to do some testing.
> One of the things that I noticed with the luceneweb web app is that when I
> searched, the search results returned "Summary" of "null", so I added:
> doc.add(new Field("summary", "FooFoo", Field.Store.YES,
> Field.Index.NOT_ANALYZED));
> to the, and ran it again.
> I had expected that I'd then be able to do a search for something like
> "summary:foofoo", but when I did that, I got no results.
> I also tried, and again got no results.
> I tried using Luke, and that is showing that the "summary" field is in the
> indexes, so I'm wondering why I am not able to search on other fields such
> as "summary", "path", etc.?
> Can anyone explain what else I need to do, esp. in the luceneweb web app, to
> be able to search these other fields?
> Thanks!
> Jim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message