Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
SolrRequest has a getBasePath & setBasePath. The naming is poor; it's the URL base to the Solr node like "http://localhost:8983/solr". It's only recognized by HttpSolrClient; LBSolrClient (used by CloudSolrClient) ignores it and will in fact mutate the passed in request to its liking, which is rather ugly because it means a request cannot be used concurrently if the user wants to. But moreover I think there's a conceptual discordance of placing this concept on SolrRequest given that some clients want to route requests to nodes they choose. I propose removing this from SolrRequest and instead adding a method specific to HttpSolrClient. Almost all existing usages of setBasePath immediately execute the request on an HttpSolrClient, so should be easy to change.
Attachments
Issue Links
- relates to
-
SOLR-17314 SolrClient implementations should not mutate request objects
- Open
- links to