You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by bu...@apache.org on 2003/06/03 21:22:27 UTC
DO NOT REPLY [Bug 20461] New: -
scores not from 0 to 1, not consistant with HitCollector
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20461>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20461
scores not from 0 to 1, not consistant with HitCollector
Summary: scores not from 0 to 1, not consistant with HitCollector
Product: Lucene
Version: 1.2
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Search
AssignedTo: lucene-dev@jakarta.apache.org
ReportedBy: daniel.armbrust@mayo.edu
I've noticed an oddity in scoring....
If I do my search like this:
searcher.search(query, filter, new HitCollector()
{
public void collect(int doc, float score)
{
tempHits.add(new LuceneHits(doc, score));
}
});
I get different scores for the resulting documents than I do if I do
my search like this:
hits = searcher.search(query, filter);
Both methods return the same number of hits. I can live with them
returning different scores, I'm just curious as to why it happens.
Furthermore, the first method returns several scores that are greater
than 1.0. Isn't this supposed to be impossible? The FAQ states that
scores range from 0 to 1.
I have a self-contained class test class I will attach shortly...
This affects the 1.3 RC's as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org