Just to clarify one point from my original response, the "df" parameter is
already set for the default request handlers, so all you need to do is
change it from the "text" field to your preferred default field.
Or, you can simply uncomment the deprecated defaultSearchField element in
your schema and you should get the old behavior.
As far as the rationale, the discussion is here:
https://issues.apache.org/jira/browse/SOLR-2724
"Deprecate defaultSearchField and defaultOperator defined in schema.xml"
In 4.x, this change was reverted, so the defaultSearchField element is
present.
The issue is still open for 4.x.
Feel free to comment directly on that Jira.
-- Jack Krupansky
-----Original Message-----
From: Rohit
Sent: Monday, June 11, 2012 9:49 AM
To: solr-user@lucene.apache.org
Subject: RE: defaultSearchField not working after upgrade to solr3.6
Hi Jack,
I understand that df would make this work normaly, but why did
defaultSearchField stop working suddenly. I notice that there is talk about
deprecating it, but even then it should continue to work right?
Regards,
Rohit
-----Original Message-----
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: 11 June 2012 18:49
To: solr-user@lucene.apache.org
Subject: Re: defaultSearchField not working after upgrade to solr3.6
Add the "df" parameter to your query request handler. It names the default
field. Or use "qf" for the edismax query parser.
-- Jack Krupansky
-----Original Message-----
From: Rohit
Sent: Monday, June 11, 2012 8:58 AM
To: solr-user@lucene.apache.org
Subject: defaultSearchField not working after upgrade to solr3.6
Hi,
We have just migrated from solr3.5 to solr3.6, for all this time we have
been querying solr as,
http://122.166.9.144:8080/solr/
<http://122.166.9.144:8080/solr/%3c%3ccorename%3e%3e/?q=apple>
<<corename>>/?q=apple
But now this is not working and the name of the search field needs to be
provided everytime, which was not the case earlier. What might be casing
this?
Regards,
Rohit
