[
https://issues.apache.org/jira/browse/NUTCH-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939503#comment-14939503
]
Julien Nioche commented on NUTCH-2129:
--------------------------------------
I'd rather keep it simple and not modify the CrawlDatum so much. Why don't you
simply add a config element and optionally store the code in the metadata?
BTW we already have the option to store the response headers - see
[https://github.com/apache/nutch/commit/23c7761aff830db82a1e44b84bf81265639c9a26].
You could use that and simply reparse the first line to get the code.
> Track Protocol Status in Crawl Datum
> ------------------------------------
>
> Key: NUTCH-2129
> URL: https://issues.apache.org/jira/browse/NUTCH-2129
> Project: Nutch
> Issue Type: Improvement
> Affects Versions: 2.3, 1.10
> Reporter: Michael Joyce
> Fix For: 2.4, 1.11
>
>
> It's become necessary on a few crawls that I run to get protocol status code
> stats. After speaking with [~lewismc] it seemed that there might not be a
> super convenient way of doing this as is, but it would be great to be able to
> add the functionality necessary to pull this information out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
