lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <>
Subject [jira] [Commented] (SOLR-3534) dismax and edismax should default to "df" when "qf" is absent.
Date Mon, 11 Jun 2012 21:39:43 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message