lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2724) Deprecate defaultSearchField and defaultOperator defined in schema.xml
Date Thu, 29 Mar 2012 03:21:43 GMT


David Smiley commented on SOLR-2724:

I take issue with the Yonik's comment "we're not really gaining anything with this change".
 I don't know about you, but I'm always pondering how Solr can work better and be easier to
understand / configure.  I don't think defaultSearchField & defaultOperator have a need
to exist, let alone exist in schema.xml, thereby creating unnecessary complexity in understanding
the product -- albeit in a small way.  My work with Erik on simplifying the solrconfig.xml
is along the same lines with my eventual hope to simply eliminate default="true" on a RH and
the handleSelect thing.

I do agree that defaultSearchField is more useful than defaultOperator, but when it is depended
on for some search or another (like the /browse fq=ipod example in SOLR-3292) , IMO it would
been better/clearer for the query to be explicit.
> Deprecate defaultSearchField and defaultOperator defined in schema.xml
> ----------------------------------------------------------------------
>                 Key: SOLR-2724
>                 URL:
>             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
>   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:!default.jspa
For more information on JIRA, see:


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

View raw message