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 Fri, 23 Mar 2012 20:29:27 GMT


David Smiley commented on SOLR-2724:

bq: Besides, I don't think there should be any expectation of "it'll just work" if you copy
some arbitrary subset of an old schema into a new example config.

>From a user's perspective:
"I know all I changed were X, Y and Z in my schema, I'll copy those to the new one and I should
be good to go. That way I'll pick up any new goodness without having to examine every line,
including ones I haven't changed." is quite reasonable IMO. Messy, but true. We have a better
argument with a major release when we say "you should have read the CHANGES.txt file".

I don't quite agree with this reasoning but I'll pretend I do for a moment.  If a user actually
didn't change the defaultSearchField "text" from the example schema.xml as you suggest in
your scenario, then I think things will probably still work.  Why?  Because the new solrconfig.xml's
search handler and other applicable handlers will have q.df=text.  They might not be using
that handler because they are using their own -- true, but I'm pointing out it's even more
unlikely than you think it is.

> 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
>   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