[
https://issues.apache.org/jira/browse/NUTCH-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613277#comment-13613277
]
Sebastian Nagel commented on NUTCH-1419:
----------------------------------------
Hi Lewis,
+1 for NUTCH-1419-trunk.patch (parsechecker and indexchecker).
For NUTCH-1419-2.x.patch (parsechecker only): the error message
{code}
2013-03-25 23:29:40,000 ERROR parse.ParserChecker - Fetch failed with protocol
status: org.apache.nutch.storage.ProtocolStatus@1b7d0 {
"code":"12"
"args":"[http://www.apachecon.eu/]";
"lastModified":"0"
}
{code}
could be improved using ProtocolStatusUtils.getName and .getMessage, cf. the
patch for indexchecker in NUTCH-1038. A "moved" or "moved(12)" is more
informative.
> parsechecker and indexchecker to report protocol status
> -------------------------------------------------------
>
> Key: NUTCH-1419
> URL: https://issues.apache.org/jira/browse/NUTCH-1419
> Project: Nutch
> Issue Type: Improvement
> Components: indexer, parser
> Affects Versions: nutchgora, 1.6
> Reporter: Sebastian Nagel
> Priority: Minor
> Fix For: 1.7, 2.2
>
> Attachments: NUTCH-1419-1.patch, NUTCH-1419-2.x.patch,
> NUTCH-1419-trunk.patch
>
>
> Parsechecker and indexchecker should report the protocol status when the
> fetch was not successful (status other than 200/ok).
> In case of a redirect, the protocol status contains the URL a redirect points
> to. Usually, this URL should be checked instead of the original one which is
> not indexed. The content of a redirect response is less useful (and often
> empty):
> {code}
> % nutch indexchecker http://lucene.apache.org/nutch/
> fetching: http://lucene.apache.org/nutch/
> parsing: http://lucene.apache.org/nutch/
> contentType: text/html
> content : 301 Moved Permanently Moved Permanently The document has
> moved here . Apache/2.4.1 (Unix) OpenSSL/1.
> title : 301 Moved Permanently
> host : lucene.apache.org
> tstamp : Tue Jul 03 13:27:32 CEST 2012
> url : http://lucene.apache.org/nutch/
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
