[
https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529628
]
Stu Hood commented on SOLR-350:
-------------------------------
I feel like the suggested implementation is a re-imagining of the Tomcat
Manager REST api (http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html).
The main reason I like the idea of multiple cores in the same instance is to
provide tighter integration between them: more like a conventional relational
database, with multiple tables that have independent schemas (where Solr core
== SQL table). Otherwise, having your servlet container managing the contexts
just makes more sense, since that is what it is built for.
Also, I think the core should be a parameter of the query, so that there is the
possibility of querying multiple cores simultaneously. Having a top-level
controller managing dispatch to the cores opens up all kinds of possibilities
for future expansion, (such as joins between indexes?) and it would make things
like federated search much more elegant. SOLR-303 already has a "shards"
parameter with the same idea behind it: just prefix local cores with the @
symbol, and you are good to go.
Loving the potential here!
> 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
>
>
> 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.
