[
https://issues.apache.org/jira/browse/NUTCH-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516428
]
Andrzej Bialecki commented on NUTCH-514:
-----------------------------------------
+1 we're only humans with 24 hours in a day .. ;)
Actually, this issue is a part of a bigger problem, i.e. how to deal with
redirected pages, and this patch doesn't solve the underlying problem. We can
add it as a band-aid for the time being, until we come up with a proper fix.
I'd suggest that the commit message includes a reference to NUTCH-273 and
NUTCH-353 .
> Indexer should only index pages with fetch status SUCCESS
> ---------------------------------------------------------
>
> Key: NUTCH-514
> URL: https://issues.apache.org/jira/browse/NUTCH-514
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Reporter: Doğacan Güney
> Priority: Minor
> Fix For: 1.0.0
>
> Attachments: NUTCH-514.patch
>
>
> Currently if you parse during fetch, nutch only parses pages which are
> successfully (i.e, have a status STATUS_FETCH_SUCCESS). But, if you run parse
> as a seperate job, nutch parses pages like "404 not found"s or "301 moved"s.
> Since most of these can be successfully parsed these are indexed and show up
> in search results.
> IMO, we should either somehow mark contents so that a separate parse doesn't
> output non-STATUS_FETCH_SUCCESS pages or we should filter them out in Indexer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nutch-developers mailing list
Nutch-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nutch-developers
