One other thing I discovered that I mention so no one else is tripped up by it.
I set the boost to zero for the categories in the query. When I ran my unit tests, some of them started to fail. I eventually realized that the failures were in searches where I only wanted to find documents in the right category (i.e., I wasn't looking for documents with any particular words in them); I would get zero hits. I'm assuming this is because even though the document belonged to a category I was looking for, because lucene computed its score as 0, it assumed I didn't want that document. I guess that all makes sense, it just means I have to be careful as to which queries I set the category boost to zero and which I don't. -----Original Message----- From: Scott Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 12, 2006 3:31 PM To: java-user@lucene.apache.org Subject: RE: de-boosting fields I've implemented the zero boost solution and it seems to be doing what I want. Thanks to everyone who had suggestions. -----Original Message----- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: Monday, December 11, 2006 11:45 AM To: java-user@lucene.apache.org Subject: Re: de-boosting fields : Isn't it also true that using Field.Index.NO_NORMS when creating the field will : remove it from the scoring formula? I thought I read that somewhere, but now : can't find where. queries on fields with NO_NORMS will still contribute to the score, but the field *length* and/or field bosts won't contribute to the score. -Hoss --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
