[
https://issues.apache.org/jira/browse/SOLR-10464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653617#comment-17653617
]
ASF subversion and git services commented on SOLR-10464:
--------------------------------------------------------
Commit f0c6549efd776ff95edcf3a2b8c8e87d9b7dcc31 in solr's branch
refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=f0c6549efd7 ]
SOLR-10464: setCollectionCacheTTL should be deprecated in favor of Solr Client
Builder methods (#1247)
migrated parameter to builder, changing it to withCollectionCacheTtl from
setCollectionCacheTtl
> setCollectionCacheTTL should be deprecated in favor of Solr Client Builder
> methods
> ----------------------------------------------------------------------------------
>
> Key: SOLR-10464
> URL: https://issues.apache.org/jira/browse/SOLR-10464
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Reporter: Jason Gerlowski
> Assignee: Eric Pugh
> Priority: Minor
> Fix For: 7.0
>
> Time Spent: 1.5h
> 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
> {{setCollectionCacheTT}} 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]
