nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Jelsma (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NUTCH-1341) NotModified time set to now but page not modified
Date Thu, 19 Apr 2012 14:54:45 GMT

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

Markus Jelsma updated NUTCH-1341:
---------------------------------

    Attachment: NUTCH-1341-1.6-1.patch

Here's a patch for 1.6. It simply resets the modifiedTime to the CrawlDatum's previous value
right after the reducers sets a STATUS_DB_NOTMODIFIED status value. Since i believe the status
is correct i assume the modifiedTime value can be reset here as well.

Please comment. Did i overlook something? Implement it differently?

Thanks
                
> NotModified time set to now but page not modified
> -------------------------------------------------
>
>                 Key: NUTCH-1341
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1341
>             Project: Nutch
>          Issue Type: Bug
>    Affects Versions: 1.5
>            Reporter: Markus Jelsma
>            Assignee: Markus Jelsma
>             Fix For: 1.6
>
>         Attachments: NUTCH-1341-1.6-1.patch
>
>
> Servers tend to respond with incorrect or no value for LastModified. By comparing signatures
or when (fetch.getStatus() == CrawlDatum.STATUS_FETCH_NOTMODIFIED) the reducer correctly sets
the db_notmodified status for the CrawlDatum. The modifiedTime value, however, is not set
accordingly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message