You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Markus Jelsma (JIRA)" <ji...@apache.org> on 2014/05/13 11:54:17 UTC

[jira] [Resolved] (NUTCH-1586) Non-db_success records should have interval.max

     [ https://issues.apache.org/jira/browse/NUTCH-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Markus Jelsma resolved NUTCH-1586.
----------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.9)

Better to solve in fetch schedule!

> 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
>         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 was sent by Atlassian JIRA
(v6.2#6252)