nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Jelsma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (NUTCH-1646) IndexerMapReduce to consider DB status
Date Tue, 01 Oct 2013 12:51:26 GMT

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

Markus Jelsma resolved NUTCH-1646.
----------------------------------

    Resolution: Fixed

Thanks.
Committed revision 1528072.


> 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-trunk.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.1#6144)

Mime
View raw message