You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/07/11 15:04:00 UTC

[jira] [Commented] (NUTCH-2976) SitemapProcessor: verify sitemap values added from sitemap to CrawlDB (priority, modification time and change frequency)

    [ https://issues.apache.org/jira/browse/NUTCH-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004718#comment-18004718 ] 

ASF GitHub Bot commented on NUTCH-2976:
---------------------------------------

sebastian-nagel opened a new pull request, #854:
URL: https://github.com/apache/nutch/pull/854

   Verify the sitemap additional values added from a sitemap to CrawlDB by SitemapProcessor: priority, modification time and change frequency.
   - use default priority if priority <= 0.0 (a CrawlDatum with score 0.0 is not eligible for fetch)
   - ensure that the fetch interval (from change frequency) is within db.fetch.schedule.adaptive.min_interval and db.fetch.schedule.adaptive.max_interval
   - ignore last-modified times in the future
   
   




> SitemapProcessor: verify sitemap values added from sitemap to CrawlDB (priority, modification time and change frequency)
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NUTCH-2976
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2976
>             Project: Nutch
>          Issue Type: Improvement
>          Components: sitemap
>    Affects Versions: 1.19
>            Reporter: Sebastian Nagel
>            Priority: Major
>             Fix For: 1.21
>
>
> SitemapProcesser writes values from the sitemap into the CrawlDB without verification or plausibility check:
> - priority - used as CrawlDatum score
> - modification time
> - change frequency - used as fetch interval
> Since these values in the sitemap cannot be trusted, the processor should make sure that they are in acceptable ranges:
> - priority > 0.0 (a score of 0.0 would cause that a URL is never fetched)
> - modification time: not in the future
> - change frequency / fetch interval within [db.fetch.schedule.adaptive.min_interval, db.fetch.schedule.max_interval]
> See also NUTCH-2975



--
This message was sent by Atlassian Jira
(v8.20.10#820010)