[
https://issues.apache.org/jira/browse/SOLR-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13296114#comment-13296114
]
David Smiley commented on SOLR-2724:
------------------------------------
I agree Jack. I spent some time wordsmithing the comments, trying to be more
descriptive but not too much. Here is what I propose:
{noformat}
<!-- DEPRECATED: The defaultSearchField is consulted by the Lucene query
parser[*] when
parsing a query string that isn't explicit about the field. Machine
(non-user)
generated queries are best made explicit, or they can use the "df" request
parameter
which takes precedence over this.
[*]: It's used by some other parsers and in a couple corners of Solr too.
Note: Un-commenting defaultSearchField will be insufficient if your request
handler
in solrconfig.xml defines "df", which takes precedence. That would need to be
removed.
<defaultSearchField>text</defaultSearchField> -->
<!-- DEPRECATED: The defaultOperator (AND|OR) is consulted by the Lucene query
parser[*]
when parsing a query string to determine if a clause of the query should be
marked as
required or optional, assuming the clause isn't already marked by some
operator.
The default is OR, which is generally assumed so it is not a good idea to
change it
globally here. The "q.op" request parameter takes precedence over this.
[*]: It's used by some other parsers and in a couple corners of Solr too.
<solrQueryParser defaultOperator="OR"/> -->
{noformat}
> Deprecate defaultSearchField and defaultOperator defined in schema.xml
> ----------------------------------------------------------------------
>
> Key: SOLR-2724
> URL: https://issues.apache.org/jira/browse/SOLR-2724
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis, search
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: 3.6, 4.0
>
> Attachments:
> SOLR-2724_deprecateDefaultSearchField_and_defaultOperator.patch,
> SOLR-2724_deprecateDefaultSearchField_and_defaultOperator.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> I've always been surprised to see the <defaultSearchField> element and
> <solrQueryParser defaultOperator="OR"/> defined in the schema.xml file since
> the first time I saw them. They just seem out of place to me since they are
> more query parser related than schema related. But not only are they
> misplaced, I feel they shouldn't exist. For query parsers, we already have a
> "df" parameter that works just fine, and explicit field references. And the
> default lucene query operator should stay at OR -- if a particular query
> wants different behavior then use q.op or simply use "OR".
> <similarity> Seems like something better placed in solrconfig.xml than in the
> schema.
> In my opinion, defaultSearchField and defaultOperator configuration elements
> should be deprecated in Solr 3.x and removed in Solr 4. And <similarity>
> should move to solrconfig.xml. I am willing to do it, provided there is
> consensus on it of course.
--
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]
