[
https://issues.apache.org/jira/browse/SOLR-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984489#comment-15984489
]
Jan Høydahl commented on SOLR-7041:
-----------------------------------
Current state of this is that you have been getting a {{WARN}} in logs since
3.6 when using these, but they still work. The attached patch (old) changes
that warn log into throwing an exception (dependent on luceneMatchVersion). But
for that to be committable all tests must also stop using these.
Since these have been deprecated for a long time, perhaps we don't need to let
the removal happen on exactly version 7.0.0, but can allow it to take place in
any minor version? Do we need a CHANGES entry in 6.6.0 that this is the last
version where you can expect it to still work?
> Nuke 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.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
