, New])
Hits is deprecated.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/browse/LUCENE-954
> Project: Lucene - Java
> Issue Type: Improve
lved.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/browse/LUCENE-954
> Project: Lucene - Java
> Issue Type: Improvement
> Com
need to work on Hits. I'll resolve this as
Won't Fix in a few days, unless somebody has some more thoughts on this.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apac
e to deprecate the Hits class, and attaches a patch
that does so and replaces examples of it's usage in the demo and tutorial, i'll
certainly vote for it.
{quote}
Done with LUCENE-1290.
I'm waiting for your vote, Hoss ;-)
> Toggle score
: Otis Gospodnetic
Unit test passes.
Will commit next week.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/browse/LUCENE-954
> Project: Lucene - Java
>
ease file a new issue if you want to see Hits (and
consequently also Hit/HitIterator) being deprecated. I do not see any reason
for this, though.
This patch is meant for helping Lucene users who currently use the Hits class
and particularly have problems with the built-in score normalization, and
age in the demo and tutorial, i'll
certainly vote for it -- but until then, if people want to try and improve
Hits, there's little reason not to do so.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
>
ecate the Hits search(Query) method, to change the
tutorials to recommend TopDocCollector instead, and to stop trying to improve
Hits.
{quote}
+1
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: h
cing yet another suggest
improvements to the Hits interface).
So I say - it's time to deprecate the Hits search(Query) method, to change the
tutorials to recommend TopDocCollector instead, and to stop trying to improve
Hits.
> Toggle score normalization in Hits
> ---
: [Patch Available, New])
Affects Version/s: 2.3
2.3.1
changed affected versions
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/br
])
Affects Version/s: 2.4
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/browse/LUCENE-954
> Project: Lucene - Java
> Issue Type: Improvement
with 2.3), and without tabs.
The patch file also includes a new testcase which demonstrates the new feature.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/br
[
https://issues.apache.org/jira/browse/LUCENE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571553#action_12571553
]
Doug Cutting commented on LUCENE-954:
-
Disabling score normalization in Hits s
On Feb 22, 2008, at 7:10 AM, Christian Kohlschütter (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571367
#action_12571367 ]
Christian Kohlschütter commented on LUCENE-954:
ed by score in descending order. With the current implementation of
Lucene Hits, these scores are not comparable across instances. With the patch,
they are (at least when score normalization is turned off).
If you need more information about the Federated Search system, we can indeed
move the dis
issue, so
I'd be happy to discuss more there and hear other thoughts. It has been a
while since I have read anything on it.
That also isn't to say that your patch isn't worthwhile, just wondering whether
the change is actually meaningful for your use case.
> To
Hits currently tries to "hide" this by normalizing the scores to a maximum of
1, simply by dividing the "raw" scores by the maximum score returned.
This is why the scores from Hits are currently not comparable to each other.
The suggested patch resolves this problem.
> To
the queryWeight part of the score (the part
the same for all documents), but not to the fieldWeight. idf and norms can
both be > 1.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.
ding this, though I don't understand why the
top-score was greater than 1 (original description above mentions this) in the
first place, since scores in Hits are normalized and thus should always be less
than 1.
> Toggle score norm
: (was: 2.2)
change the version
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/browse/LUCENE-954
> Project: Lucene - Java
> Is
score normalization.
> Toggle score normalization in Hits
> --
>
> Key: LUCENE-954
> URL: https://issues.apache.org/jira/browse/LUCENE-954
> Project: Lucene - Java
> Issue Type: Improvement
Toggle score normalization in Hits
--
Key: LUCENE-954
URL: https://issues.apache.org/jira/browse/LUCENE-954
Project: Lucene - Java
Issue Type: Improvement
Components: Search
Affects Versions
A couple of things about score normalization...
a) search(weight,filter,ndocs) does not do normalization
b) search(weight,filter,ndocs,sort) does do normalization... even if the
sort is by score only
c) because of (b), the normalized scores given by MultiSearcher.search
(weight,filter,ndocs,sort
Never mind... my mistake.
FieldSortedHitQueue takes care of tracking maxscore and normalizes the score
in fillFields().
-Yonik
On 9/21/05, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
> Hits does normalization based on the score of the first document
> "scoreDocs[0].score"
> This is a problem if sor
Hits does normalization based on the score of the first document
"scoreDocs[0].score"
This is a problem if sort is on anything other than score, since the first
document won't necessarily be the highest scoring.
I propose fixing this by adding a field to TopDocs called "maxScore", and
using that i
25 matches
Mail list logo
