[
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
backup of my local state: added untested code (create core dynamically), still
some thinking to be done (using CoreDescriptor as vehicle for multicore
serialization in&out?)
As for the added complexity versus the swap command, I believe the potential
functional benefits make it worth it.
Using the URL (and not parameters) to carry information is good practice and
seems like an appropriate rationale; for instance, using the 'alias' through
the URL to map query behaviors (be it, filtered queries, query parsers, etc)
would open to easy ways to fit per-user/usage profiles behaviors.
And I think we can be informative enough on misconfiguration so users know
exactly where the error sit.
> 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, 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.
