You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "epugh (via GitHub)" <gi...@apache.org> on 2023/02/20 01:30:08 UTC

[GitHub] [solr] epugh commented on pull request #1353: SOLR-16563 DefaultCollectionSolrClient

epugh commented on PR #1353:
URL: https://github.com/apache/solr/pull/1353#issuecomment-1436173735

   @dsmiley I tried using the `DefaultCollectionSolrClient` with out much success.  Everywhere wanted a CloudSolrClient...   Or, I didn't have setters in the testing infrastructure to take in a `DefaultCollectionSolrClient`....    So not sure here.
   
   I am now wondering if having `setDefaultCollection` is that bad?   Maybe it's okay to have it there.  Or, rip the band-aid off and force the use of collectionName everywhere?   At least, in our test infrastrutture?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org