Hi Markus,
<lst name="debug">
<str name="rawquerystring">awstats</str>
<str name="querystring">awstats</str>
<str name="parsedquery">content:awstat</str>
<str name="parsedquery_toString">content:awstat</str>
?
<lst name="explain">
?
<str name="http://www.tachtler.net/de_app.navi.01.analysistools.do";>
0.023213852 = (MATCH) fieldWeight(content:awstat in 7), product of:
2.0 = tf(termFreq(content:awstat)=4)
3.9618306 = idf(docFreq=2, maxDocs=58)
0.0029296875 = fieldNorm(field=content, doc=7)
</str>
?
<str name="http://www.tachtler.net/en_app.navi.01.analysistools.do";>
0.0 = (MATCH) fieldWeight(content:awstat in 35), product of:
2.0 = tf(termFreq(content:awstat)=4)
3.9618306 = idf(docFreq=2, maxDocs=58)
0.0 = fieldNorm(field=content, doc=35)
</str>
</lst>
Yes, this makes sense! Looks like Nutch is sending a 0 boost on the document
or field which results in a 0 score. Index-time boosting is a part
of fieldNorm.
You can either use omitNorms in Solr on those fields to work around
the problem
(note, there won't be length normalization anymore) or try to see
why Nutch is
doing this. I've seen this before but didn't find the cause.
what about the configuration in nutch-default.xml -->
...
<property>
<name>query.lang.boost</name>
<value>0.0</value>
<description> Used as a boost for lang field in Lucene query.
</description>
</property>
...
could this be helpful ?!?
Klaus.
--
------------------------------------------------
e-Mail : [email protected]
Homepage: http://www.tachtler.net
DokuWiki: http://www.dokuwiki.tachtler.net
------------------------------------------------
