lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Woodward (JIRA)" <>
Subject [jira] [Commented] (SOLR-6894) Add MultiCoreSolrServer
Date Mon, 29 Dec 2014 16:05:13 GMT


Alan Woodward commented on SOLR-6894:

I looked at changing the SolrServer API to allow for this, but it isn't easy.  We'd need to
add an additional method taking a core or collection name to every existing method on the
API, and to be honest I think there's enough cruft there as it is.  And I really dislike the
'default collection' implementation on CloudSolrServer, which means that nothing is thread-safe.

Although thinking about it, maybe the .forCore() method should be added directly to the SolrServer
API?  And then CloudSolrServer could also implement a .forCollection() method that just forwards
to it.  Or .forCollection() returns another CloudSolrServer, but .forCore() returns an HttpSolrServer?
 Or is this just making things over-complicated?

> Add MultiCoreSolrServer 
> ------------------------
>                 Key: SOLR-6894
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrJ
>    Affects Versions: 5.0, Trunk
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Minor
>         Attachments: SOLR-6894.patch
> At the moment, it isn't possible to use a single SolrServer instance to create new cores
via CoreAdmin on an empty node, and then query those nodes.  MultiCoreSolrServer is a utility
class that does just that, by allowing you to create child SolrServer instances for individual
cores that share the underlying HttpClient.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message