You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Kay Kay (JIRA)" <ji...@apache.org> on 2009/01/14 19:25:59 UTC
[jira] Updated: (SOLR-960) CommonsHttpSolrServer - documentation -
phase II (Addition of log in setMaxRetries as a warning for out of range
input)
[ https://issues.apache.org/jira/browse/SOLR-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kay Kay updated SOLR-960:
-------------------------
Attachment: SOLR-960.patch
> CommonsHttpSolrServer - documentation - phase II (Addition of log in setMaxRetries as a warning for out of range input)
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-960
> URL: https://issues.apache.org/jira/browse/SOLR-960
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Reporter: Kay Kay
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-960.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Add javadoc for :
> CommonsHttpSolrServer#AGENT
> CommonsHttpSolrServer#_invariantParams
> CommonsHttpSolrServer#_followRedirects
> CommonsHttpSolrServer#_allowCompression , _maxRetries
> #setConnectionTimeout, #setSoTimeout
> #setConnectionManagerTimeout(int) deprecated in favor of #setConnectionManagerTimeout(long) with the same API as in HttpClient 3.1 .
> #setMaxRetries - there would be a warning in the log message if the maximum retries were > 1 to keep the programmer explicitly aware of the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.