Hmmm... how could I have gotten so confused?!?! Actually, I recognized my
mistake yesterday (after reading the code some more for David's Jira) but
hadn't gotten around to correcting myself.
In any case, the original problematic scenario may have been simply copying
3.5 request handler/params to the 3.6 example solrconfig but not realizing
that the deprecated defaultSearchField element needed to be uncommented in
the 3.6 schema.
A second scenario was using in fact setting defaultSearchField but it wasn't
working - because the request handler for 3.6 had set df to "text" and the
code won't check the defaultSearchField if "df" is set.
-- Jack Krupansky
-----Original Message-----
From: Chris Hostetter
Sent: Thursday, June 14, 2012 4:05 PM
To: solr-user@lucene.apache.org
Subject: Re: defaultSearchField not working after upgrade to solr3.6
: Correct. In 3.6 it is simply ignored. In 4.x it currently does work.
That's not true.
the example cofigs in Solr 3.6 no longer mention defaultSearchField,
but Solr 3.6 will still respect a <defaultSearchField/> declaration if
it exists in your schema.xml -- I just verified this by running Solr 3.6
using hte Solr 3.5 example configs.
The only change SOLR-2274 made to the *CODE* in 3.6 was to improve the
wording in the logs/error messages to better distiguish when it was
refering to the "df" param vs the "<defaultSearchField/>"
Rohit: if you are running 3.6 wit ha schema.xml that contains a
<defaultSearchField> and you are seeing a failure related to not fiding
hte default field, please post your schema.xml and the stack trace of the
error.
-Hoss
