[ https://issues.apache.org/jira/browse/SOLR-16563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687518#comment-17687518 ]
David Smiley commented on SOLR-16563: ------------------------------------- See https://github.com/apache/solr/pull/1353 One challenge to using it is that there are bound to be some places that expect a particular subclass of SolrClient. That's the crux of the down-side here versus baking this idea into SolrClient (thus every subclass). > 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 > Time Spent: 10m > Remaining Estimate: 0h > > 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