[SOLR-4196] Untangle XML-specific nature of Config and Container classes

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 4.3, 6.0
• Component/s: Schema and Analysis
• Assignee: Erick Erickson
• Reporter: Erick Erickson
• Created: 15/Dec/12 12:09
• Updated: 09/May/16 18:43
• Resolved: 02/Apr/13 01:02

Description

sub-task for SOLR-4083. If we're going to try to obsolete solr.xml, we need to pull all of the specific XML processing out of Config and Container. Currently, we refer to xpaths all over the place. This JIRA is about providing a thunking layer to isolate the XML-esque nature of solr.xml and allow a simple properties file to be used instead which will lead, eventually, to solr.xml going away.

Issue Links

• breaks: SOLR-4960 race condition in CoreContainer.shutdown leads to double closes on cores
• is related to: SOLR-4400 Rapidly opening and closing cores can lead to deadlock
• is related to: SOLR-1028 Automatic core loading unloading for multicore
• is related to: SOLR-4083 Deprecate specifying individual <core> information in solr.xml. Possibly deprecate solr.xml entirely
• is related to: SOLR-4749 Refactor the new solr.xml and core discovery code.
• relates to: SOLR-4401 Move the stress test in SOLR-4196 into a junit test
• supercedes: SOLR-1293 Support for large no:of cores and faster loading/unloading of cores
• supercedes: SOLR-1533 Partition data directories into multiple "bucket" directories
• supercedes: SOLR-4083 Deprecate specifying individual <core> information in solr.xml. Possibly deprecate solr.xml entirely
• supercedes: SOLR-4301 Consolidate lazily-loaded cores and loadOnStartup cores lists into a separate class
• supercedes: SOLR-4013 Creating a core should prevent more than one thread from creating a core of the same name at once.