You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Kelvin Tan (JIRA)" <ji...@apache.org> on 2005/03/11 23:27:52 UTC
[jira] Created: (NUTCH-8) fetcher.retry.max no longer in use
fetcher.retry.max no longer in use
----------------------------------
Key: NUTCH-8
URL: http://issues.apache.org/jira/browse/NUTCH-8
Project: Nutch
Type: Bug
Reporter: Kelvin Tan
Priority: Minor
In current Subversion code, the configuration entry fetcher.retry.max is no longer being used. It should either be removed from nutch-default.xml, or the functionality (re-)implemented in Fetcher.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (NUTCH-8) fetcher.retry.max no longer in use
Posted by "Stefan Grroschupf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/NUTCH-8?page=history ]
Stefan Grroschupf updated NUTCH-8:
----------------------------------
Attachment: retry_patch.txt
A patch.
Value is now used in updatedatabasetool.
HTH,
Stefan
> fetcher.retry.max no longer in use
> ----------------------------------
>
> Key: NUTCH-8
> URL: http://issues.apache.org/jira/browse/NUTCH-8
> Project: Nutch
> Type: Bug
> Reporter: Kelvin Tan
> Priority: Minor
> Attachments: retry_patch.txt
>
> In current Subversion code, the configuration entry fetcher.retry.max is no longer being used. It should either be removed from nutch-default.xml, or the functionality (re-)implemented in Fetcher.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (NUTCH-8) fetcher.retry.max no longer in use
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/NUTCH-8?page=history ]
Doug Cutting resolved NUTCH-8:
------------------------------
Resolution: Fixed
This was a feature of an obsolete version of the fetcher. Therre is a related feature of the updatedb tool that was not configurable. So I removed this parameter and replaced it with a configurable parameter for the updatedb tool.
Fixed in revision 157453.
http://svn.apache.org/viewcvs.cgi?rev=157453&view=rev
> fetcher.retry.max no longer in use
> ----------------------------------
>
> Key: NUTCH-8
> URL: http://issues.apache.org/jira/browse/NUTCH-8
> Project: Nutch
> Type: Bug
> Reporter: Kelvin Tan
> Priority: Minor
> Attachments: retry_patch.txt
>
> In current Subversion code, the configuration entry fetcher.retry.max is no longer being used. It should either be removed from nutch-default.xml, or the functionality (re-)implemented in Fetcher.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira