[ 
https://issues.apache.org/jira/browse/SOLR-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811242#comment-13811242
 ] 

David Smiley commented on SOLR-2724:
------------------------------------

I just checked but I'm not seeing it in 
./example/solr/collection1/conf/schema.xml which is the main reference schema.  
The multicore example still has that.  I'm more of the opinion ./multicore 
should be simply omitted altogether than improved.

I'm not surprised some tests depend on some schemas having these defaults.  
These schema elements were marked deprecated which means they are discouraged 
but still supported.  They were written before SOLR-2724, most likely.  Nothing 
should fundamentally depend on these being specified in schema.xml; there are 
other better places like 'df' & 'q.op' in local-params. 

> 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-ALPHA
>
>         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 was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to