You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/01 02:57:04 UTC

[jira] [Commented] (NUTCH-2129) Track Protocol Status in Crawl Datum

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

ASF GitHub Bot commented on NUTCH-2129:
---------------------------------------

GitHub user MJJoyce opened a pull request:

    https://github.com/apache/nutch/pull/68

    NUTCH-2129 - Add protocol status tracking to crawl datum

    - Add protocol status information to CrawlDatum.
    - Bump CrawlDatum version number.
    - Save HTTP Protocol status in CrawlDatum in lib-http.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/MJJoyce/nutch NUTCH-2129

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nutch/pull/68.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #68
    
----
commit d4c6d864752f17eeac0cb34032502e28743e3d17
Author: Michael Joyce <ml...@gmail.com>
Date:   2015-10-01T00:50:55Z

    NUTCH-2129 - Add protocol status tracking to crawl datum
    
    - Add protocol status information to CrawlDatum.
    - Bump CrawlDatum version number.
    - Save HTTP Protocol status in CrawlDatum in lib-http.

----


> 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)