[
https://issues.apache.org/jira/browse/NUTCH-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969919#comment-15969919
]
Hudson commented on NUTCH-2132:
-------------------------------
FAILURE: Integrated in Jenkins build Nutch-trunk #3425 (See
[https://builds.apache.org/job/Nutch-trunk/3425/])
Fixes for NUTCH-2132: Added the library amqp (gitRoann3l;fhdez:
[https://github.com/apache/nutch/commit/9d65ac6d6b33d83e1fc9ab387f29a3287b0b26b3])
* (edit) src/plugin/publish-rabbitmq/plugin.xml
Fixes for NUTCH-2132: Added new properties (gitRoann3l;fhdez:
[https://github.com/apache/nutch/commit/bc9a2c859c2b2036aa58d899c529cbf6282a41df])
* (edit) conf/nutch-default.xml
* (edit)
src/plugin/publish-rabbitmq/src/java/org/apache/nutch/publisher/rabbitmq/RabbitMQPublisherImpl.java
Fixes for NUTCH-2132: Deleted empty comments (gitRoann3l;fhdez:
[https://github.com/apache/nutch/commit/5eb77a9de6d20f31a5fd6759022b25552744cc16])
* (edit)
src/plugin/publish-rabbitmq/src/java/org/apache/nutch/publisher/rabbitmq/RabbitMQPublisherImpl.java
Fixes for NUTCH-2132: Fixed the default port (gitRoann3l;fhdez:
[https://github.com/apache/nutch/commit/ee651752295468af75a14f6c98686c0d7c26136a])
* (edit) conf/nutch-default.xml
* (edit)
src/plugin/publish-rabbitmq/src/java/org/apache/nutch/publisher/rabbitmq/RabbitMQPublisherImpl.java
> 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.15#6346)
