[
https://issues.apache.org/jira/browse/NUTCH-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432469#comment-15432469
]
Hudson commented on NUTCH-2242:
-------------------------------
FAILURE: Integrated in Jenkins build Nutch-trunk #3393 (See
[https://builds.apache.org/job/Nutch-trunk/3393/])
NUTCH-2164 NUTCH-2242 Inconsistent 'Modified Time' in crawl db / (snagel: rev
70622c3e18cee879f5a38d895f68dd0be69461e1)
* (edit) src/java/org/apache/nutch/crawl/DefaultFetchSchedule.java
* (edit) src/java/org/apache/nutch/protocol/ProtocolOutput.java
* (edit) src/java/org/apache/nutch/crawl/AdaptiveFetchSchedule.java
* (edit) src/test/org/apache/nutch/crawl/TestCrawlDbStates.java
> 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.13
>
> 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)
