[
https://issues.apache.org/jira/browse/SOLR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293111#comment-13293111
]
Jack Krupansky commented on SOLR-3534:
--------------------------------------
Okay, but if df does not have a default value, then at least have it throw an
exception at an early stage, like core/handler load, rather than result in
queries with an empty field name that returns zero results as it does today.
Although, I suppose it is possible that a particular application may intend to
set df explicitly on each request and not need/want a default. But, even in
that case, I think an exception should be thrown rather than accept an empty
field name and silently provide zero search results.
I am still in favor of "text" as the hardwired default. Isn't "text" the
traditional default search field? Including in the Solr example schema.
But, that said, I will certainly defer to the rest of the Solr community.
> dismax and edismax should default to "df" when "qf" is absent.
> --------------------------------------------------------------
>
> Key: SOLR-3534
> URL: https://issues.apache.org/jira/browse/SOLR-3534
> Project: Solr
> Issue Type: Improvement
> Components: query parsers
> Affects Versions: 4.0
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
>
> The dismax and edismax query parsers should default to "df" when the "qf"
> parameter is absent. They only use the defaultSearchField in schema.xml as a
> fallback now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
