[
https://issues.apache.org/jira/browse/NUTCH-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doğacan Güney updated NUTCH-514:
--------------------------------
Attachment: NUTCH-514.patch
A simple patch for the issue. Updates Indexer to check for STATUS_FETCH_SUCCESS.
I will let this patch stay here for a while. Is having 404 and 301 (and
similar) pages in search results useful to anyone? Also, should we skip them in
parser or filter them in indexer (as this patch does)?
> 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 DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nutch-developers mailing list
Nutch-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nutch-developers
