lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: When using Dismax, Solr 5.1 tries to compare the entire field to the search string, instead of only using keywords
Date Thu, 04 Jun 2015 12:52:11 GMT
On 6/4/2015 1:22 AM, Wouter Admiraal wrote:
> When I turn on debug, I get the following:
> "debug": {
>   "rawquerystring": "Food",
>   "querystring": "Food",
>   "parsedquery": "(+DisjunctionMaxQuery((label:Food^3.0)) ())/no_coord",
>   "parsedquery_toString": "+(label:Food^3.0) ()",
>   "explain": {},
>   "QParser": "DisMaxQParser",
>   "altquerystring": null,
>   "boostfuncs": null,
>   ...
> }
> I don't understand how/why this doesn't use a "contains" operator.
> This was the behavior on the old 1.4 instance. I went through the
> changelog for 1.4 to 5.1, but I don't find any explicit information
> about dismax behaving differently, except the "mm" parameter needs a
> default. I tried many values for mm (including 0, 100%, 100, etc) but
> to no avail.

In your schema.xml, what is the definition of the label field, and the
fieldType definition of the type used in the label field?  That will
determine exactly how the query is parsed and whether individual words
will match.  I wasn't using dismax or edismax back when I was running
1.4, so I can't say anything about how it used to work, only how it
works now.


View raw message