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 2016/05/11 08:21:12 UTC
[jira] [Updated] (NUTCH-2242) lastModified not always set
[ https://issues.apache.org/jira/browse/NUTCH-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-2242:
---------------------------------
Fix Version/s: 1.12
> lastModified not always set
> ---------------------------
>
> Key: NUTCH-2242
> URL: https://issues.apache.org/jira/browse/NUTCH-2242
> Project: Nutch
> Issue Type: Bug
> Components: crawldb
> Affects Versions: 1.11
> Reporter: Jurian Broertjes
> Priority: Minor
> Fix For: 1.12
>
> Attachments: NUTCH-2242.patch
>
>
> I observed two issues:
> - When using the DefaultFetchSchedule, CrawlDatum's modifiedTime field is not updated on the first successful fetch.
> - When a document modification is detected (protocol- or signature-wise), the modifiedTime isn't updated
> I can provide a patch later today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)