[jira] [Updated] (SOLR-8975) SolrClient setters should be deprecated in favor of Solr Client Builder methods

["Eric Pugh (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-8975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Pugh updated SOLR-8975:
----------------------------
    Summary: SolrClient setters should be deprecated in favor of Solr Client Builder methods  (was: SolrClient setters should be deprecated in favor of SolrClientBuilder methods)

> SolrClient setters should be deprecated in favor of Solr Client Builder methods
> -------------------------------------------------------------------------------
>
>                 Key: SOLR-8975
>                 URL: https://issues.apache.org/jira/browse/SOLR-8975
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrJ
>            Reporter: Jason Gerlowski
>            Priority: Minor
>         Attachments: SOLR-8975.patch
>
>          Time Spent: 7h 40m
>  Remaining Estimate: 0h
>
> SOLR-8097 added a builder layer on top of each {{SolrClient}} implementation.
> Now that builders are in place for SolrClients, the setters used in each SolrClient can be deprecated, and their functionality moved over to the Builders.  This change brings a few benefits:
> - unifies SolrClient configuration under the new Builders.  It'll be nice to have all the knobs, and levers used to tweak SolrClients available in a single place (the Builders).
> - reduces SolrClient thread-safety concerns.  Currently, clients are mutable.  Using some SolrClient setters can result in erratic and "trappy" behavior when the clients are used across multiple threads.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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