[jira] Commented: (NUTCH-963) Add support for deleting Solr documents with STATUS_DB_GONE in CrawlDB (404 urls)

["Markus Jelsma (JIRA)" <ji...@apache.org>]

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

Markus Jelsma commented on NUTCH-963:
-------------------------------------

Julien, shouldn't the deduplicate mechanism kept separate from purging 404's? I agree your proposal for finding dupes is better than the current but i believe it should be kept separate because:
- people may use a Solr update request processor for finding and deleting dupes (it has several hashing algorithm incl. a fuzzy matching)
- controlled environments where there are no dupes don't need a 404 purger that wastes cycles on finding dupes

If so, i believe this issue can be committed for 1.3 after further testing.

> Add support for deleting Solr documents with STATUS_DB_GONE in CrawlDB (404 urls)
> ---------------------------------------------------------------------------------
>
>                 Key: NUTCH-963
>                 URL: https://issues.apache.org/jira/browse/NUTCH-963
>             Project: Nutch
>          Issue Type: New Feature
>          Components: indexer
>    Affects Versions: 2.0
>            Reporter: Claudio Martella
>            Assignee: Markus Jelsma
>            Priority: Minor
>             Fix For: 1.3, 2.0
>
>         Attachments: NUTCH-963-command-and-log4j.patch, Solr404Deleter.java, SolrClean.java
>
>
> When issuing recrawls it can happen that certain urls have expired (i.e. URLs that don't exist anymore and return 404).
> This patch creates a new command in the indexer that scans the crawldb looking for these urls and issues delete commands to SOLR.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira