Christine Poerschke created SOLR-13611:
------------------------------------------
Summary: deprecated <solrcloud> vs. replacement
<updateshardhandler> elements
Key: SOLR-13611
URL: https://issues.apache.org/jira/browse/SOLR-13611
Project: Solr
Issue Type: Task
Reporter: Christine Poerschke
In
[SolrXmlConfig.fromConfig|https://github.com/apache/lucene-solr/blob/releases/lucene-solr/8.1.0/solr/core/src/java/org/apache/solr/core/SolrXmlConfig.java#L73-L97]
the {{deprecatedUpdateConfig}} naming and usage suggests that some
{{<solrcloud>}} elements e.g. {{distribUpdateSoTimeout}} are deprecated in
favour of a {{<updateshardhandler>}} element with the same name.
The
[solr.xml|https://github.com/apache/lucene-solr/blob/releases/lucene-solr/8.1.0/solr/server/solr/solr.xml]
included in our releases and the
[documentation|https://lucene.apache.org/solr/guide/8_1/format-of-solr-xml.html]
still use what would then appear to be the deprecated of the two choices and
as far as I can tell no warnings about this are logged on Solr startup.
This ticket here is to start a pathway via which support for the deprecated
choice would eventually be removed e.g. future 8.x releases could WARN if the
deprecated choice is used and then in 9.x releases support would be removed and
an exception thrown if the deprecated choice is still encountered in a
{{solr.xml}} file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
