[
https://issues.apache.org/jira/browse/SOLR-13719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916061#comment-16916061
]
Shawn Heisey commented on SOLR-13719:
-------------------------------------
Looks like we have an oversight in SolrClient and its children - there should
be a ping method that takes a collection name. Variants like this exist for
most of the functionality provided by SolrClient.
I can think of two workarounds until that happens:
1) The setDefaultCollection method, which should work quite well for
deployments with one collection. I do not see any evidence that this method is
slated for removal.
2) Code like this, which directs to a specific collection:
{noformat}
SolrPingResponse rsp = new SolrPing().process(client, collection);
{noformat}
> SolrClient.ping() in 8.2, using SolrJ
> -------------------------------------
>
> Key: SOLR-13719
> URL: https://issues.apache.org/jira/browse/SOLR-13719
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: clients - java
> Affects Versions: 8.2
> Environment: linux mint 19, java8
> Reporter: Benjamin Wade Friedman
> Priority: Trivial
> Labels: beginner, easyfix, newbie
>
> {color:#222222}I started a local SolrCloud instance with two nodes and two
> replicas per node. I created one empty collection on each node. So I guess
> I have two shard per collection.
> {color}
>
> I tried to use the ping method in Solrj to verify my connected client. When
> I try to use it, it throws ...
>
> Caused by: org.apache.solr.common.SolrException: No collection param
> specified on request and no default collection has been set: []
> at
> org.apache.solr.client.solrj.impl.BaseCloudSolrClient.sendRequest(BaseCloudSolrClient.java:1071)
> ~[solr-solrj-8.2.0.jar:8.2.0 31d7ec7bbfdcd2c4cc61d9d35e962165410b65fe -
> ivera - 2019-07-19 15:11:07]
>
> I cannot pass a collection name to the ping request. And the
> CloudSolrClient.Builder does not allow me to declare a default collection.
> {color:#222222}BaseCloudSolrClient.setDefault{color}{color:#222222}{color:#222222}Collection(String)
> is effectively deprecated because CloudSolrClient no longer has a public
> constructor. {color}{color}
>
> {color:#222222}{color:#222222}Can we add an argument to the Builder
> constructor to accept a string for the default collection? Or a new setter
> on the Builder? {color}{color}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
