lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <>
Subject [jira] [Commented] (SOLR-6840) Remove legacy solr.xml mode
Date Thu, 25 Dec 2014 19:29:13 GMT


Alexandre Rafalovitch commented on SOLR-6840:

Probably not caught by the tests, but the DIH example uses the legacy form of solr.xml. Somebody
need to add empty files, etc. The only issue is that one of the cores was
declared as default, not sure if any examples rely on this.

> Remove legacy solr.xml mode
> ---------------------------
>                 Key: SOLR-6840
>                 URL:
>             Project: Solr
>          Issue Type: Task
>            Reporter: Steve Rowe
>            Assignee: Erick Erickson
>            Priority: Blocker
>             Fix For: 5.0
>         Attachments: SOLR-6840.patch, SOLR-6840.patch
> On the [Solr Cores and solr.xml page|],
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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message