[
https://issues.apache.org/jira/browse/NUTCH-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471126#comment-15471126
]
Hudson commented on NUTCH-2132:
-------------------------------
SUCCESS: Integrated in Jenkins build Nutch-trunk #3395 (See
[https://builds.apache.org/job/Nutch-trunk/3395/])
Fix for NUTCH-2132: Publisher/Subscriber model for Nutch to emit events,
(sujen: rev e53b34b2322f2d071981a72577644a225642ecbc)
* (add) src/plugin/publish-rabbitmq/build-ivy.xml
* (add)
src/plugin/publish-rabbitmq/src/java/org/apache/nutch/publisher/rabbitmq/package-info.java
* (add) src/java/org/apache/nutch/fetcher/FetcherThreadPublisher.java
* (edit) src/plugin/build.xml
* (edit) src/java/org/apache/nutch/fetcher/FetcherThread.java
* (add) src/java/org/apache/nutch/publisher/NutchPublisher.java
* (edit) src/plugin/nutch-extensionpoints/plugin.xml
* (edit) conf/nutch-default.xml
* (edit) ivy/ivy.xml
* (add) src/java/org/apache/nutch/fetcher/FetcherThreadEvent.java
* (add) src/plugin/publish-rabbitmq/plugin.xml
* (edit) src/java/org/apache/nutch/metadata/Nutch.java
* (add)
src/plugin/publish-rabbitmq/src/java/org/apache/nutch/publisher/rabbitmq/RabbitMQPublisherImpl.java
* (edit) build.xml
* (add) src/plugin/publish-rabbitmq/build.xml
* (add) src/java/org/apache/nutch/publisher/NutchPublishers.java
* (add) src/plugin/publish-rabbitmq/ivy.xml
> Publisher/Subscriber model for Nutch to emit events
> ----------------------------------------------------
>
> Key: NUTCH-2132
> URL: https://issues.apache.org/jira/browse/NUTCH-2132
> 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
(v6.3.4#6332)
