: >> We did some tests with omitNorms=false. We have seen that in the last
: >> result's page we have some scores set to 0.0. This scores setted to 0 are
: >> problematic to our sorters.
: >>
: >> It could be some kind of bug?
It could be, but it isn't neccessarily.
"0.0" is a perfectly legal s
We have just tested it with the last version of Solr and we still have
scores to 0.
adeelmahmood wrote:
>
> I was gonna ask a question about this but you seem like you might have the
> answer for me .. wat exactly is the omitNorms field do (or is expected to
> do) .. also if you could please h
http://wiki.apache.org/lucene-java/ConceptsAndDefinitions
On Thu, Feb 18, 2010 at 7:13 AM, Raimon Bosch wrote:
>
>
> I am not an expert in lucene scoring formula, but omintNorms=false makes the
> scoring formula a little bit more complex, taking into account boosting for
> fields and documents. I
I am not an expert in lucene scoring formula, but omintNorms=false makes the
scoring formula a little bit more complex, taking into account boosting for
fields and documents. If I'm not wrong (if I am please, correct me) I think
that with omitNorms=false take into account the queryNorm(q) and nor
I was gonna ask a question about this but you seem like you might have the
answer for me .. wat exactly is the omitNorms field do (or is expected to
do) .. also if you could please help me understand what termVectors and
multiValued options do ??
Thanks for ur help
Raimon Bosch wrote:
>
>
> Hi
Hi,
We did some tests with omitNorms=false. We have seen that in the last
result's page we have some scores set to 0.0. This scores setted to 0 are
problematic to our sorters.
It could be some kind of bug?
Regrads,
Raimon Bosch.
--
View this message in context:
http://old.nabble.com/some-sco
