My bad... In changing my code to use unstored fields, i introduced a bug where I wasn't tokenizing correctly. changing Field.Text(name, value) to new Field(name, value, true, false, true) in too many places led to a couple cases of inconsistency.
thanks for the reply. > -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 24, 2004 1:58 PM > To: Lucene Users List > Subject: Re: field indexed but not stored > > > On Jun 24, 2004, at 2:10 PM, Ryan Sonnek wrote: > > I'm using lucene-1.4-rc3 and trying to optimize the size of > our index > > and decrease search times. our index has several fields > that we need > > to search and sort by, but only one field that we actually retrieve > > from the hits document. I tried creating all fields as unstored, > > except for the one I need, except now all searches fail (0 > results). > > Is this the correct way to do this or did I misunderstand the > > documentation? > > Perhaps you converted some Keyword fields to Unstored? If > that is the > case, then you added tokenization which might be getting in > the way of > what you expect. > > Could you provide an example of what you indexed and how you are > searching? (succinct code works the best to remove ambiguity) > > 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]
