[
https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991517#comment-15991517
]
Jan Høydahl commented on SOLR-7041:
-----------------------------------
Skimmed through SOLR-2724. It's a long time since these discussions and also a
long time since the 3.6 deprecation of these schema features.
What is the sentiment now, in particular from [~hossman] and
[~yo...@apache.org]? The code handling {{defaultOperator}} or
{{defaultSearchField}} in schema will go away in 7.0, and we'll fail-fast if we
encounter these from 6.6 (silently ignoring would be worse than failing).
Personally I haven't used these for years. But the main reason I started
working on this is that it feels good to actually remove deprecated stuff and
simplify the code, config and complexity of the product. But I don't have a
problem either with just leaving it in there forever, as seemed to be what some
of you (strongly) wanted way back then. If I get serious, well-founded
push-back now, I'll unassign myself and leave the fate of this change in the
hands of [~dsmiley] :-)
> Remove defaultSearchField and solrQueryParser from schema
> ---------------------------------------------------------
>
> Key: SOLR-7041
> URL: https://issues.apache.org/jira/browse/SOLR-7041
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 6.0
>
> Attachments: SOLR-7041-defaultOperator.patch, SOLR-7041.patch
>
>
> The two tags {{<defautlSearchField>}} and {{solrQueryParser}} were deprecated
> in Solr3.6 (SOLR-2724). Time to nuke them from code and {{schema.xml}} in 5.0?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
