[
https://issues.apache.org/jira/browse/SOLR-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350461#comment-14350461
]
Alan Woodward commented on SOLR-7201:
-------------------------------------
You can still create an HttpSolrClient pointing at a core, but core-specific
queries won't work in that case. I don't think we want to add
setDefaultCollection here though. The problem is, there's no way to know from
just the passed-in URL string if we're pointing at the container app or at a
specific core.
I'll add some JavaDoc to the class explaining the different use-cases:
* create an HttpSolrClient pointing to a specific core (can't do core admin
requests or requests to another core)
* create an HttpSolrClient pointing to the container app (can do core admin
requests, all core-specific requests should use the core-specific request
methods)
> Implement multicore handling on HttpSolrClient
> ----------------------------------------------
>
> Key: SOLR-7201
> URL: https://issues.apache.org/jira/browse/SOLR-7201
> Project: Solr
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Minor
> Attachments: SOLR-7201.patch
>
>
> Now that SOLR-7155 has added a collection parameter to the various SolrClient
> methods, we can let HttpSolrClient use it to allow easier multicore handling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
