[SOLR-1621] Allow current single core deployments to be specified by solr.xml

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5
• Fix Version/s: 1.5, 3.1, 4.0-ALPHA
• Assignee: Noble Paul
• Reporter: Noble Paul
• Created: 04/Dec/09 04:24
• Updated: 30/Mar/11 15:45
• Resolved: 15/Dec/09 07:06

Description

supporting two different modes of deployments is turning out to be hard. This leads to duplication of code. Moreover there is a lot of confusion on where do we put common configuration. See the mail thread http://markmail.org/message/3m3rqvp2ckausjnf

Issue Links

• is depended upon by: SOLR-1277 Implement a Solr specific naming service (using Zookeeper)
• relates to: SOLR-1626 Solr doesn't differentiate between a primary core and an alias
• relates to: SOLR-1722 Allowing changing the "special" default core name, and as a default default core name, switch to using collection1 rather than DEFAULT_CORE

Sub-Tasks

• Remove ALIAS command: Closed