You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (JIRA)" <ji...@apache.org> on 2018/07/23 12:02:00 UTC
[jira] [Updated] (NUTCH-1926) AdaptiveFetchScheduler reads
nutch-default settings as float but it needs integer.
[ https://issues.apache.org/jira/browse/NUTCH-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Nagel updated NUTCH-1926:
-----------------------------------
Fix Version/s: 1.16
2.4
> AdaptiveFetchScheduler reads nutch-default settings as float but it needs integer.
> ----------------------------------------------------------------------------------
>
> Key: NUTCH-1926
> URL: https://issues.apache.org/jira/browse/NUTCH-1926
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 2.3, 1.9
> Reporter: Lewis John McGibbney
> Assignee: Talat UYARER
> Priority: Major
> Fix For: 2.4, 1.16
>
>
> This issue is document as [follows|http://www.mail-archive.com/dev%40nutch.apache.org/msg16088.html]
> {code}
> > - AdaptiveFetchSchedular do not work. In default settings float, it needs
> > integer.
> Confirmed, in nutch-default.xml these two properties are defined as floats
> but read as integers. Configuration.getInt(name) then returns the default value.
> <name>db.fetch.schedule.adaptive.min_interval</name>
> <value>60.0</value>
> <name>db.fetch.schedule.adaptive.max_interval</name>
> <value>31536000.0</value>
> Is there already a Jira open? The problem applies to 1.x and 2.x.
> But it's hardly a blocker: the default values are also 60 and 31536000.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)