[ https://issues.apache.org/jira/browse/NUTCH-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15059750#comment-15059750 ]
Markus Jelsma edited comment on NUTCH-2184 at 12/16/15 9:43 AM: ---------------------------------------------------------------- Hello Lewis - keep in mind the possible configurations for index.*.md and db.parsemeta.to.crawldb. Different settings may lead to peculiar situations. - index everything for index.parse.md - force to load content file if index.content.md is present - what to do with db.parsemeta.to.crawldb? Also, what is going to happen to transient errors? Records with FETCH_STATUS_RETRY should be ignored. was (Author: markus17): Hello Lewis - keep in mind the possible configurations for index.*.md and db.parsemeta.to.crawldb. Different settings may lead to peculiar situations. > Enable IndexingJob to function with no crawldb > ---------------------------------------------- > > Key: NUTCH-2184 > URL: https://issues.apache.org/jira/browse/NUTCH-2184 > Project: Nutch > Issue Type: Improvement > Components: indexer > Reporter: Lewis John McGibbney > Assignee: Lewis John McGibbney > Fix For: 1.12 > > Attachments: NUTCH-2184.patch > > > Sometimes when working with distributed team(s), we have found that we can > 'loose' data structures which are currently considered as critical e.g. > crawldb, linkdb and/or segments. > In my current scenario I have a requirement to index segment data with no > accompanying crawldb or linkdb. > Absence of the latter is OK as linkdb is optional however currently in > [IndexerMapReduce|https://github.com/apache/nutch/blob/trunk/src/java/org/apache/nutch/indexer/IndexerMapReduce.java] > crawldb is mandatory. > This ticket should enhance the IndexerMapReduce code to support the use case > where you ONLY have segments and want to force an index for every record > present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)