[
https://issues.apache.org/jira/browse/NUTCH-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883504#action_12883504
]
Alex McLintock commented on NUTCH-774:
--------------------------------------
> pushing this out per http://bit.ly/c7tBv9
I can't see that these patches have been applied and committed to the trunk. So
I don't think this is included in release 1.1
Sounds like this one is still open and is a simple fix.
> Retry interval in crawl date is set to 0
> ----------------------------------------
>
> Key: NUTCH-774
> URL: https://issues.apache.org/jira/browse/NUTCH-774
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.0.0
> Reporter: Reinhard Schwab
> Assignee: Andrzej Bialecki
> Attachments: NUTCH-774.patch, NUTCH-774_2.patch
>
>
> When i fetch and parse a feed with the feed plugin,
> http://www.wachauclimbing.net/home/impressum-disclaimer/feed/
> another crawl date is generated
> http://www.wachauclimbing.net/home/impressum-disclaimer/comment-page-1/
> after fetching a second round
> the dump in the crawl db still shows a retry interval with value 0.
> http://www.wachauclimbing.net/home/impressum-disclaimer/comment-page-1/
> Version: 7
> Status: 2 (db_fetched)
> Fetch time: Wed Dec 02 12:48:22 CET 2009
> Modified time: Thu Jan 01 01:00:00 CET 1970
> Retries since fetch: 0
> Retry interval: 0 seconds (0 days)
> Score: 1.0833334
> Signature: db9ab2193924cd2d0b53113a500ca604
> Metadata: _pst_: success(1), lastModified=0
> a check should be done in DefaultFetchSchedule (or AbstractFetchSchedule) in
> the
> method
> setFetchSchedule
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
