[
https://issues.apache.org/jira/browse/SOLR-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276996#comment-14276996
]
Mark Miller commented on SOLR-6840:
-----------------------------------
bq saying "Scheme 'http' not registered",
Perhaps something assuming http for an address when it needs to use a call to
get http or https.
> Remove legacy solr.xml mode
> ---------------------------
>
> Key: SOLR-6840
> URL: https://issues.apache.org/jira/browse/SOLR-6840
> Project: Solr
> Issue Type: Task
> Reporter: Steve Rowe
> Assignee: Erick Erickson
> Priority: Blocker
> Fix For: 5.0
>
> Attachments: SOLR-6840.patch, SOLR-6840.patch, SOLR-6840.patch,
> SOLR-6840.patch
>
>
> On the [Solr Cores and solr.xml
> page|https://cwiki.apache.org/confluence/display/solr/Solr+Cores+and+solr.xml],
> the Solr Reference Guide says:
> {quote}
> Starting in Solr 4.3, Solr will maintain two distinct formats for
> {{solr.xml}}, the _legacy_ and _discovery_ modes. The former is the format we
> have become accustomed to in which all of the cores one wishes to define in a
> Solr instance are defined in {{solr.xml}} in
> {{<cores><core/>...<core/></cores>}} tags. This format will continue to be
> supported through the entire 4.x code line.
> As of Solr 5.0 this form of solr.xml will no longer be supported. Instead
> Solr will support _core discovery_. [...]
> The new "core discovery mode" structure for solr.xml will become mandatory as
> of Solr 5.0, see: Format of solr.xml.
> {quote}
> AFAICT, nothing has been done to remove legacy {{solr.xml}} mode from 5.0 or
> trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
