You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (JIRA)" <ji...@apache.org> on 2014/03/07 19:19:43 UTC

[jira] [Resolved] (NUTCH-1646) IndexerMapReduce to consider DB status

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

Sebastian Nagel resolved NUTCH-1646.
------------------------------------

    Resolution: Fixed

fix with NUTCH-1706

> IndexerMapReduce to consider DB status
> --------------------------------------
>
>                 Key: NUTCH-1646
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1646
>             Project: Nutch
>          Issue Type: Bug
>          Components: indexer
>    Affects Versions: 1.7
>            Reporter: Markus Jelsma
>            Assignee: Markus Jelsma
>             Fix For: 1.8
>
>         Attachments: NUTCH-1646-2.patch, NUTCH-1646-3.patch, NUTCH-1646-trunk.patch, NUTCH-1646.patch
>
>
> IndexerMapReduce does not remove gone and redirects via DB status, only fetch status. This means segments merged before we fixed SegmentMerger may contain records that do not have a correct status. For example, some pages are gone on the web, gone in the CrawlDB, gone in the segments. But merging those old segments could cause a older status to prevail, causing it to be indexed although the CrawlDB says it's gone.



--
This message was sent by Atlassian JIRA
(v6.2#6252)