"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
: 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 declaration if
it exists in your schema.xml -- I just verified this by running Solr 3.6
using hte Sol
]
Sent: 11 June 2012 20:35
To: solr-user@lucene.apache.org
Subject: Re: defaultSearchField not working after upgrade to solr3.6
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
@lucene.apache.org
Subject: Re: defaultSearchField not working after upgrade to solr3.6
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 pre
eld 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 s
...@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 Krup
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 afte
