[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-350:
-------------------------------
Attachment: solr-350.patch
Looking good. I took your patch and removed all the 'default' stuff to make it
in line with Hoss' observations in:
http://www.nabble.com/Re%3A-purpose-of-MultiCore-%22default%22---p14591921.html
This adds the dispatcher settings to multicore.xml
{code:xml}
<multicore adminPath="/admin/multicore" dataDir="alldata" persistent="true" >
<abortOnConfigurationError>true</abortOnConfigurationError>
<requestDispatcher handleSelect="true" >
<requestParsers enableRemoteStreaming="false"
multipartUploadLimitInKB="2048" />
</requestDispatcher>
<core name="core0" instanceDir="core0" default="true"/>
<core name="core1" instanceDir="core1"/>
</multicore>
{code}
The one thing we need to change before commiting is how the test work with
multicore-base.xml and multicore.xml -- maybe the 'clean' copy should live in
the test files and get copied over on a shutdown hook? We want to make sure
everythign in the /examples directory helps people understand how things work.
> 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-Naming.patch,
> solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch,
> solr-350.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.
