[
https://issues.apache.org/jira/browse/SOLR-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051758#comment-16051758
]
Jan Høydahl commented on SOLR-10903:
------------------------------------
Quoting [my suggestion from
SOLR-10574|https://issues.apache.org/jira/browse/SOLR-10574?focusedCommentId=16049575&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16049575].
Guess this could be done both with "simple" and "edismax" parsers, but thought
"simple" was -- eh ... simpler :) :
{quote}Let's consider an ability for the ootb default configsets to auto search
all fields if neither {{df}} or {{qf}} are specified. A potential fast-track
solution is to extend {{SimpleQParserPlugin}} to interpret {{qf=\*}} as a
catch-all mode where it simply iterates all indexed fields in schema and
searches across these. We could then add to our {{/select}} and {{/query}}
handlers in the default config sets: {{defType=simple&qf=*}}...
{quote}
To make this less intrusive the catch-all mode could be triggered only if
{{qf=*}} is explicitly configured, something we could enable by default in the
data driven config sets. Then it is easy to turn it off my editing qf and df in
the request handlers.
> Default configuration should use edismax for searching on all fields
> --------------------------------------------------------------------
>
> Key: SOLR-10903
> URL: https://issues.apache.org/jira/browse/SOLR-10903
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Fix For: master (7.0)
>
>
> An offshoot from discussions at SOLR-10574.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
