[
https://issues.apache.org/jira/browse/SOLR-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295303#comment-13295303
]
Hoss Man commented on SOLR-3534:
--------------------------------
bq. I'll presume that you don't mean "<defaultSearchField/>" literally, you
mean "<defaultSearchField>text</defaultSearchField/>".
yes, sorry .. i was using "<defaultSearchField/>" as shorthand for
<defaultSearchField>...something...</defaultSearchField/>, that was bad on my
part and totally confusing.
bq. So are you effectively saying that schema-minimal.xml should add a
defaultSearchField to it?
No, i'm saying that as long as "<defaultSearchField>...</defaultSearchField/>"
is legal and supported configuration, then this specific test (of
"dismaxNoDefaults") should use a schema that has a
"<defaultSearchField>...</defaultSearchField/>" in it since that's the point of
the test.
schema-minimal.xml should certainly not have a "<defaultSearchField>..." added,
since that would no longer truely be a minimal schema.xml
> 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
> Attachments:
> SOLR-3534_dismax_and_edismax_should_default_to_df_if_qf_is_absent.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
