[ https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Biestro updated SOLR-350: ------------------------------- Attachment: solr-350.patch updated to implement 'alias' (should be considered draft since there aren't specific unit tests associated yet); implements persistence (added an XmlWriter that might be revisited); all operations that modify the multicore state will rewrite the multicore.xml Alias feature: 0 - Name and aliases reside in a common identifier space; one identifier uniquely determines a core (can't have the identifier 'core' used a a name to point to coreA and as an alias to point to coreB) 1 - One core has one unique immutable name (rename command has been neutralized) 2 - One core may have many aliases 3 - There are only 2 admin commands related to aliases: 3.1 - alias(core, alias): adds an alias to a core, overriding any existing alias but fails to override a core name. 3.2 - unalias(str); if str is a core name identifier, all its aliases get deleted, if str is an alias identifer only that alias gets deleted. 4 - Core addressing through URLs/API can use either name or alias (although using alias is best practice for common -aka non-admin- operations) > Manage Multiple SolrCores > ------------------------- > > Key: SOLR-350 > URL: https://issues.apache.org/jira/browse/SOLR-350 > Project: Solr > Issue Type: Improvement > Affects Versions: 1.3 > Reporter: Ryan McKinley > Attachments: SOLR-350-MultiCore.patch, SOLR-350-MultiCore.patch, > SOLR-350-MultiCore.patch, SOLR-350-Naming.patch, solr-350.patch, > solr-350.patch, solr-350.patch > > > In SOLR-215, we enabled support for more then one SolrCore - but there is no > way to use them yet. > We need to make some interface to manage, register, modify avaliable SolrCores -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.