Re: Boosting Fields (in index) or Queries

2006-04-14 Thread Jeremy Hanna
I still have a similar problem with the boost factor. I change the name to have the AND operator and set that query's boost to a very high value in relation to the others. I also have a regular OR based name so that it doesn't rule those out. However whenever I change the boost values wi

Re: Boosting Fields (in index) or Queries

2006-04-14 Thread Michael D. Curtin
Jeremy Hanna wrote: I would use a database function to force the ordering like the one your provided that works in Oracle, but it doesn't look like mysql 5 supports that. If anyone else knows of a way to force the ordering using mysql 5 queries, please respond. I think I'll just resort th

Re: Boosting Fields (in index) or Queries

2006-04-14 Thread Jeremy Hanna
hing we needed for presentation within the Lucene index. We saw a net performance increase AND simpler code when we did this. -Mike -Original Message- From: Jeremy Hanna [mailto:[EMAIL PROTECTED] Sent: Fri 4/14/06 1:15 PM To: java-user@lucene.apache.org Cc: Subject: Re:

RE: Boosting Fields (in index) or Queries

2006-04-14 Thread Bryzek.Michael
ND simpler code when we did this. -Mike -Original Message- From: Jeremy Hanna [mailto:[EMAIL PROTECTED] Sent: Fri 4/14/06 1:15 PM To: java-user@lucene.apache.org Cc: Subject: Re: Boosting Fields (in index) or Queries Wow, I finally found out why I was getting results in

Re: Boosting Fields (in index) or Queries

2006-04-14 Thread Jeremy Hanna
Wow, I finally found out why I was getting results in the wrong order - I got the results in the correct order from the Lucene index. I got the explanation of each of the results along with their database id and found the ordering mismatch. The problem is in the database call. I am calling

Re: Boosting Fields (in index) or Queries

2006-04-13 Thread Erik Hatcher
On Apr 13, 2006, at 8:55 PM, Jeremy Hanna wrote: Looking at the results, the first document in the results should hopefully be near the bottom and the Explanation for this document has a Description/Details (using the toString() on the Explanation) of: product of: 0.0 = sum of: 0.0 =

Re: Boosting Fields (in index) or Queries

2006-04-13 Thread Jeremy Hanna
Thanks for the tip. I'm trying to decipher what the explanation tells me right now. Btw, here is the code that I'm currently running: QueryParser nameParser = new QueryParser("name", analyzer); QueryParser categoryParser = new QueryParser("category", analyzer); QueryParser descripti

Re: Boosting Fields (in index) or Queries

2006-04-13 Thread Erik Hatcher
The best recommendation is to have a look at the Explanation returned from IndexSearcher.explain() for a specific query and document to trace how things are being scored. Is it possible you're boosting all documents by the same amount? Erik On Apr 13, 2006, at 6:29 PM, Jeremy Han

Boosting Fields (in index) or Queries

2006-04-13 Thread Jeremy Hanna
I have a situation where I'm indexing database entries and have fields such as: name sku model category name description features specifications I am trying to set a priority higher for the name, category name, and description. I've tried setting the fields' boost values as I've indexed th

Boosting Fields (in index) or Queries

2006-04-13 Thread Jeremy Hanna
I have a situation where I'm indexing database entries and have fields such as: name sku model category name description features specifications I am trying to set a priority higher for the name, category name, and description. I've tried setting the fields' boost values as I've indexed th