Good afternoon,

We are running some queries against a default query field (of type text) that can be expected to be multiple words.

For example, after parsing the query form I'm left with something something like this:

abstract: mouse genome informatics

The strange behavior that I am seeing however is that solr (either via the DisMaxQueryParser... or something unknown at this time) is really just running the first whitespace delimited word of this query against the indexes.

So, in theory all of the following queries are functionally equivalent:

abstract: mouse
abstract: mouse genome
abstract: mouse wouiweiopqeuqwiopdjakldjkldjklasdj k23jl12k3jkl123j

Now based on my previous work with Lucene, this is not how I would have expected a query like this to act. I would have expected Solr to have basically OR'd the words together against that field (by default, unless you change the default operand to AND) Then when it comes time to score the results Solr would generally favor the matches that match multiple words in the query over single matches, etc and so forth.

As a side note, I've taken my query right down to the basics and run it against the Solr admin, and I'm seeing the same type of results. I've also taken the query concept over to a friends project, and run it against one of his default fields and we are seeing the same behavior.

So, I must be missing something in the documentation, or something along those lines, and I figure I'd probably best post the question out there.

For multi word queries, against the default text type field what exactly happens in a multi word non phrase query? Furthermore where in the Solr documentation is this distinction spelled out?

Thank you for your time,

Matt


Reply via email to