[
https://issues.apache.org/jira/browse/SOLR-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262653#comment-14262653
]
Yonik Seeley commented on SOLR-6894:
------------------------------------
Oh, I see what you mean by forCore/forCollection now. I like it!
bq. but on a CloudSolrClient it will return a client that talks to a specific
core in the cluster, with a default parameter of distrib=false, which is useful
for debugging.
Or, more generally, forCore/forCollection could take default parameters as an
argument:
x.forCore("core1", params("distrib",false, "wt","json", "indent",true) )
Although it's difficult today to add additional parameters on update requests,
so we should really think about adding that capability too:
client.add( sdoc, params("commitWithin",5000, "_version_",1, ...) )
> Introduce SolrNodeClient API
> ----------------------------
>
> Key: SOLR-6894
> URL: https://issues.apache.org/jira/browse/SOLR-6894
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
