lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nawab Zada Asad Iqbal <khi...@gmail.com>
Subject Re: Solr 7.3 debug/explain with boost applied
Date Tue, 24 Apr 2018 20:21:39 GMT
I didn't know you can add boosts like that (&boost=2 ). Are you boosting on
a field or document by using that syntax?

On Sun, Apr 22, 2018 at 10:51 PM, Ryan Yacyshyn <ryan.yacyshyn@gmail.com>
wrote:

> Hi all,
>
> When viewing the explain under debug=true in Solr 7.3.0 using
> the edismax query parser with a boost, I only see the "boost" part of the
> explain. Without applying a boost I see the full explain. Is this the
> expected behaviour?
>
> Here's how to check using the techproducts example..
>
> bin/solr -e techproducts
>
> ```
> http://localhost:8983/solr/techproducts/select?q={!
> edismax}samsung&qf=name&debug=true
> ```
>
> returns:
>
> ```
> "debug": {
>     "rawquerystring": "{!edismax}samsung",
>     "querystring": "{!edismax}samsung",
>     "parsedquery": "+DisjunctionMaxQuery((name:samsung))",
>     "parsedquery_toString": "+(name:samsung)",
>     "explain": {
>       "SP2514N": "\n2.3669035 = weight(name:samsung in 1)
> [SchemaSimilarity], result of:\n  2.3669035 = score(doc=1,freq=1.0 =
> termFreq=1.0\n), product of:\n    2.6855774 = idf, computed as log(1 +
> (docCount - docFreq + 0.5) / (docFreq + 0.5)) from:\n      1.0 = docFreq\n
>     21.0 = docCount\n    0.8813388 = tfNorm, computed as (freq * (k1 + 1))
> / (freq + k1 * (1 - b + b * fieldLength / avgFieldLength)) from:\n      1.0
> = termFreq=1.0\n      1.2 = parameter k1\n      0.75 = parameter b\n
> 7.5238094 = avgFieldLength\n      10.0 = fieldLength\n"
>     },
>     "QParser": "ExtendedDismaxQParser",
> ...
> ```
>
> If I just add &boost=2 to this, I get this explain back:
>
> ```
> "debug": {
>     "rawquerystring": "{!edismax}samsung",
>     "querystring": "{!edismax}samsung",
>     "parsedquery": "FunctionScoreQuery(FunctionScoreQuery(+(name:samsung),
> scored by boost(const(2))))",
>     "parsedquery_toString": "FunctionScoreQuery(+(name:samsung), scored by
> boost(const(2)))",
>     "explain": {
>       "SP2514N": "\n4.733807 = product of:\n  1.0 = boost\n  4.733807 =
> boost(const(2))\n"
>     },
>     "QParser": "ExtendedDismaxQParser",
> ...
> ```
>
> Is this normal? I was expecting to see more like the first example, with
> the addition of the boost applied.
>
> Thanks,
> Ryan
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message