Chris Hostetter wrote:
if you are using a HitCollector, there any re-evaluation is going to
happen in your code using whatever mechanism you want -- once your collect
method is called on a docid, Lucene is done with that docid and no longer
cares about it ... it's only whatever storage you may b
: Thanks Erick, I've been using TopDocs, but am playing with my own HitCollector
: variant of TopDocHitCollector. The problem is not adjusting the score, it's
: what to adjust it by, i.e. is it possible to re-evaluate the scores of H1 and
H2
: knowing that the original query resulted in hits on H
Erick Erickson wrote:
Don't know if it's useful or not, but if you used TopDocs instead,
you have access to an array of ScoreDoc which you could modify
freely. In my app, I used a FieldSortedHitQueue to re-sort things
when I needed to.
Thanks Erick, I've been using TopDocs, but am playing with
Don't know if it's useful or not, but if you used TopDocs instead,
you have access to an array of ScoreDoc which you could modify
freely. In my app, I used a FieldSortedHitQueue to re-sort things
when I needed to.
ERick
On 3/22/07, Antony Bowesman <[EMAIL PROTECTED]> wrote:
I have indexed obj
I have indexed objects that contain one or more attachments. Each attachment is
indexed as a separate Document along with the object metadata.
When I make a search, I may get hits in more than one Document that refer to the
same object. I have a HitCollector which knows if the object has alre
