Hi iorixxx, Thanks a lot for your reply I had read the link and I understand the concern, however, the normalization is happening inside lucene. Where the normalizing value is the inverse of the maxScore.
I can alter the code to leave the original score, however it is a business requirements to view the matching percentage. Also, the absolute score means nothing because we wont know the exact matching score. I am thinking of alter the core to make the normalization relative to the number of terms, considering that the each term will score 1, so the exact match should score 3 if there are 3 terms. The problem for that, I dont know how to get the number of Clauses from Query, nor the number of Terms. Also, some exact matching results scored more than 3 !! any ideas? -- View this message in context: http://lucene.472066.n3.nabble.com/Search-Score-percentage-Should-not-be-relative-to-the-highest-score-tp2183420p2183784.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
