Yeah, I actually don't use the default field at all.
Well I learned something new and good today ^^ I just need to recheck
my assumptions on how Solr works versus how core lucene worked and I
think I'll be fine.
The way solr is doing it makes sense too in a way, so I just need to
readjust m
Nope, you've got it right. Parenthesis are what's necessary. This is
actually similar to the Lucene world if you consider in
your config to be equivalent to specifying a default field when
you instantiate a parser. But that's a stretch.
That said, it is surprising that you are getting the exa
Oh and to clarify what I expect to see.
I expect to see the term in a multiword query to be put together with
OR's (Unless I've set the default to be AND's in the solrconfig.xml)
I'm guessing that what I'm going to need to do here is place all of my
queries in parentheses for the fields that
I'm getting the result set that matches what it would be if I just
searched for the first word in the query.
So I'm getting the results for mouse.
And yes, abstract: is the name of the field.
So a search for
abstract: mouse
would yield 69103 results
abstract: mouse anythingelseIputhere
yiel
7;t really say what
you do see. Are you getting zero results, or fewer than you expected, or
only results that match all fields (the AND proposition)?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Multi-Word-searches-in-Solr-tp1918802p1918915.html
Sent from the Solr - User mailing list archive at Nabble.com.
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 seein
