nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doğacan Güney (JIRA) <j...@apache.org>
Subject [jira] Resolved: (NUTCH-532) CrawlDbMerger: wrong computation of last fetch time
Date Mon, 03 Sep 2007 13:38:58 GMT

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

Doğacan Güney resolved NUTCH-532.
---------------------------------

    Resolution: Fixed

Committed in rev. 572335 with minor style modifications.

> CrawlDbMerger: wrong computation of last fetch time
> ---------------------------------------------------
>
>                 Key: NUTCH-532
>                 URL: https://issues.apache.org/jira/browse/NUTCH-532
>             Project: Nutch
>          Issue Type: Bug
>            Reporter: Emmanuel Joke
>            Assignee: Emmanuel Joke
>             Fix For: 1.0.0
>
>         Attachments: NUTCH-532-test.patch, NUTCH-532.patch, NUTCH-532_v2.patch, NUTCH-532_v3.patch,
NUTCH-532_v4.patch
>
>
> CrawlDbMerger.reduce analyse the last fetch time of each record and keep the more recent
record.
> This comparison is based on a FetchInterval in days : resTime = res.getFetchTime() -
Math.round(res.getFetchInterval() * 3600 * 24 * 1000);
> It was not really a noticeable as the Math.Round method return the INTEGER.MAX_VALUE
i.e 25 days.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message