Thanks for the responses everyone. They helped lead me to my real problem. Which I suspect is the typical uber newb mistake. I was indexing with SimpleAnalyzer and searching with StandardAnalyzer.
So we are now indexing AND searching with StandardAnalyzer and things are working beautifully. Thanks again, pdk ----- Original Message ----- From: "Erik Hatcher" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Tuesday, January 13, 2004 7:10 PM Subject: Re: StandardAnalyzer and numbers indexed as text > On Jan 13, 2004, at 6:19 PM, Patrick Kates wrote: > > I have a text field called ACTIVE_YEAR that stores (of course) a year > > like > > 2003. When I index this field I can see the number in my index (using > > Luke) > > but I can't search it. If I add a text character to the end of the > > field > > and index it (200x) I can then search and find 'x', but not any > > portion of > > the number. > > Is it possible you're using a Keyword field for indexing, but an > analyzer at query time that is ripping off the number? Try the latest > Luke (0.4) and you'll see the query expression that it got parsed to on > the Search tab. The results may tell the tale. > > > One finally piece of info, when using Luke to view the terms contained > > in > > the index I can find my 'x' term, but none of the years are listed as > > terms. > > > > Any ideas on how to fix this? > > Be careful how you index and query. Field.Keyword sounds like what you > want for indexing. But for querying, QueryParser has some nasty habits > of analyzing everything. Do some Query.toString debugging if you are > using QueryParser - therein likely lies the clues to the problem. > > Erik > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
