[SOLR-10456] timeout-related setters should be deprecated in favor of SolrClientBuilder methods

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 7.0
• Component/s: SolrJ
• Assignee: Anshum Gupta
• Reporter: Jason Gerlowski
• Created: 07/Apr/17 16:41
• Updated: 02/Oct/17 10:30
• Resolved: 04/Jul/17 16:37

Description

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 setConnectionTimeout and setSoTimeout setters on all SolrClient implementations.

Issue Links

• breaks: SOLR-11425 SolrClientBuilder does not allow infinite timeout (value 0)
• is duplicated by: SOLR-10457 setSoTimeout should be deprecated in favor of SolrClientBuilder methods