[jira] Updated: (NUTCH-532) CrawlDbMerger: wrong computation of last fetch time

["Emmanuel Joke (JIRA)" <ji...@apache.org>]

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

Emmanuel Joke updated NUTCH-532:
--------------------------------

    Attachment: NUTCH-532_v2.patch

New patch provided

*  Add new method to CrawlDatum calculateLastFetchTime() and setFetchTimeBasedOnInterval(long time)

* Change the Fetch Interval from Float to Int.

* Update the different classes regardings the modifcation listed above

* Fixed the AdaptiveFetchSchedule and CrawlDbMerger convertion bug.


> 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.patch, NUTCH-532_v2.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.