[
https://issues.apache.org/jira/browse/SOLR-16563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686746#comment-17686746
]
David Smiley commented on SOLR-16563:
-------------------------------------
I looked hard but can't find a recent proposal I did in Jira-- I don't think I
proposed it in Slack. But I did find a better synthesis of my proposal in the
description of SOLR-12502
This JIRA issue could implement my CollectionSolrClient proposal (a wrapper
SolrClient), without having to spread the defaultCollection feature to any
existing SolrClient (as that seems controversial maybe). I could do a
first-draft if there is doubt on what it'd look like.
> Http2SolrClient should have a defaultCollection setting
> -------------------------------------------------------
>
> Key: SOLR-16563
> URL: https://issues.apache.org/jira/browse/SOLR-16563
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: David Smiley
> Assignee: Eric Pugh
> Priority: Minor
>
> Similar to CloudSolrClient, Http2SolrClient ought to have a
> "defaultCollection" setting. This ought to be used in preference to passing
> a "baseUrl" with this collection/core embedded into it. Maybe the builder's
> constructor should be overloaded to have a baseUrl + defaultCollection pair
> as well.
> Doing this would make it easier to issue an admin or any other node level
> command using the same SolrClient instance, just as is possible with
> CloudSolrClient and EmbeddedSolrServer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
