[
https://issues.apache.org/jira/browse/SOLR-10470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653355#comment-17653355
]
ASF subversion and git services commented on SOLR-10470:
--------------------------------------------------------
Commit ac578775e39dc0fc4abd89a1bc1bfe9424533e3c in solr's branch
refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=ac578775e39 ]
SOLR-10470: setParallelCacheRefreshes should be deprecated in favor of
SolrClientBuilder methods (#1248)
Introduce Builder setter for parallelCacheRefreshes on cloud SolrClients.
Deprecated direct setter setParallelCacheRefreshes on cloud SolrClients.
Inlined logic for creating object locks.
> setParallelCacheRefreshes should be deprecated in favor of SolrClientBuilder
> methods
> ------------------------------------------------------------------------------------
>
> Key: SOLR-10470
> URL: https://issues.apache.org/jira/browse/SOLR-10470
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Reporter: Jason Gerlowski
> Priority: Minor
> Fix For: 7.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> 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 {{SolrClient}}s 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 subtask endeavors to change this behavior for the
> {{setParallelCacheRefreshes}} setter on all {{SolrClient}} implementations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
