[
https://issues.apache.org/jira/browse/NUTCH-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jelsma updated NUTCH-1586:
---------------------------------
Attachment: NUTCH-1586.patch
Here's a new patch for trunk. The selected scheduler can still mess with the
set maxInterval but with this patch the fetchTime is actually correctly set for
redirects.
> Non-db_success records should have interval.max
> -----------------------------------------------
>
> Key: NUTCH-1586
> URL: https://issues.apache.org/jira/browse/NUTCH-1586
> Project: Nutch
> Issue Type: Bug
> Components: crawldb
> Affects Versions: 1.7
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.8
>
> Attachments: NUTCH-1586.patch, NUTCH-1586.patch
>
>
> When your default interval is low (e.g. when you start low using adaptive
> scheduling), records with redirect or gone status keep the default interval.
> There should be a switch to force 404's and redirects to use the max interval
> instead because these are usually the least interesting records for
> recrawling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
