nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NUTCH-2132) Publisher/Subscriber model for Nutch to emit events
Date Fri, 19 Aug 2016 21:08:21 GMT


ASF GitHub Bot commented on NUTCH-2132:

Github user lewismc commented on a diff in the pull request:
    --- Diff: src/java/org/apache/nutch/metadata/ ---
    @@ -95,4 +95,11 @@
     	public static final String ARG_SEGMENTDIR = "segment_dir";
     	/** Argument key to specify the location of individual segment for the REST endpoints
     	public static final String ARG_SEGMENT = "segment";
    +	/** Metadata used for the FetcherThreadEvent for publishing to subscribers*/
    +	public static final String FETCH_EVENT_TITLE = "title";
    +	public static final String FETCH_EVENT_CONTENTTYPE = "content-type";
    +	public static final String FETCH_EVENT_SCORE = "score";
    --- End diff --
    Javadoc for all of these.

> Publisher/Subscriber model for Nutch to emit events 
> ----------------------------------------------------
>                 Key: NUTCH-2132
>                 URL:
>             Project: Nutch
>          Issue Type: New Feature
>          Components: fetcher, REST_api
>            Reporter: Sujen Shah
>            Assignee: Chris A. Mattmann
>              Labels: memex
>             Fix For: 1.13
>         Attachments: NUTCH-2132.patch, NUTCH-2132.v2.patch, PubSub_routingkey.patch
> It would be nice to have a Pub/Sub model in Nutch to emit certain events (ex- Fetcher
events like fetch-start, fetch-end, a fetch report which may contain data like outlinks of
the current fetched url, score, etc). 
> A consumer of this functionality could use this data to generate real time visualization
and generate statics of the crawl without having to wait for the fetch round to finish. 
> The REST API could contain an endpoint which would respond with a url to which a client
could subscribe to get the fetcher events. 

This message was sent by Atlassian JIRA

View raw message