OK, phew :)
Mike
On Mon, Jul 20, 2009 at 7:27 AM, Raimon Bosch wrote:
>
>
> Yes, seems this bug. We are using boolean queries.
>
>
> Michael McCandless-2 wrote:
>>
>> Actually, were you seeing the 0 scores only on boolean queries? If so
>> it could be this bug that you were hitting:
>>
>> http
Yes, seems this bug. We are using boolean queries.
Michael McCandless-2 wrote:
>
> Actually, were you seeing the 0 scores only on boolean queries? If so
> it could be this bug that you were hitting:
>
> https://issues.apache.org/jira/browse/LUCENE-1744
>
> That bug only existed in trunk,
Actually, were you seeing the 0 scores only on boolean queries? If so
it could be this bug that you were hitting:
https://issues.apache.org/jira/browse/LUCENE-1744
That bug only existed in trunk, and is now fixed.
Mike
On Mon, Jul 20, 2009 at 4:53 AM, Raimon Bosch wrote:
>
>
> In our use-cas
In our use-case we are not using filterCache and documentCache in our
solrconfig.xml because we are interested in the maximum random repetitions.
That's the reason to don't use caches.
Maybe that was the reason to get 0s in the ScoreCachingWrapper.
Michael McCandless-2 wrote:
>
> It's odd tha
It's odd that this was necessary.
The ScoreCachingWrapperScorer simply wraps (and caches) the result
from calling score(), per hit, so that if score() is called more than
once we don't have to re-compute it. I don't understand why you were
always seeing 0 score come back from it.
Mike
On Thu, J
It Worked for me changing:
public void setScorer(Scorer scorer) {
this.scorer = new ScoreCachingWrappingScorer(scorer);
}
by
public void setScorer(Scorer scorer) {
this.scorer = scorer;
}
in my PseudoRandomFieldComparator.
Regards,
Raimon Bosch.
Raimon Bosch wrote:
>
> Hi,
>
Hi,
I've just implemented my PseudoRandomFieldComparator (migrated from
PseudoRandomComparatorSource) on Solr. The problem that I see is that I
don't have acces to the relevance's scores like in the deprecated class
ComparatorSource.
I saw that the TopFieldCollector is filling the scorer of my
P
