gerlowskija opened a new pull request, #2177:
URL: https://github.com/apache/solr/pull/2177

   https://issues.apache.org/jira/browse/SOLR-17066
   
   
   # Description
   
   SOLR-17066 recently expanded the concept of a "default collection" to all 
SolrClient implementations, as a migration path for folks away from baking core 
or collection names into the baseURL provided to clients.
   
   This (unreleased) change still has a drawback though: clients still have 
issues with making "admin" (i.e. core-agnostic) requests, since the SolrClient 
path-building logic always adds a collection to the path.  It doesn't have any 
way to differentiate between core-aware (e.g. `/select`, `/update`, `/config`) 
and core-agnostic (e.g. `/admin/info/health`) requests.
   
   # Solution
   
   This PR fixes this by adding a boolean metadata method to SolrRequest, 
called `requiresDataStore()`, which allows SolrClients to only selectively use 
the defaultCollection for requests that are supposed to be use a 
core/collection.
   
   # Tests
   
   Manual tests continue to pass.  Minor unit test in `SolrClientTest`.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my 
code conforms to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [x] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended)
   - [x] I have developed this patch against the `main` branch.
   - [ ] I have run `./gradlew check`.
   - [x] I have added tests for my changes.
   - [x] I have added documentation for the [Reference 
Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide)
   


-- 
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-unsubscr...@solr.apache.org

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


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

Reply via email to