[
https://issues.apache.org/jira/browse/NUTCH-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975090#comment-14975090
]
Aron Ahmadia commented on NUTCH-2132:
-------------------------------------
I tried to reconfigure the queue using the REST API:
cc = nutch.Nutch().Configs()
overrides = {
"publisher.queue.type": "rabbitmq",
"rabbitmq.exchange.server": queue_name,
"rabbitmq.exchange.type": "direct",
"rabbitmq.host": "localhost",
"rabbitmq.queue.routingkey": queue_name,
}
cc[NUTCH_CONFIG_ID] = overrides
print("Overrode configuration {} with {}".format(NUTCH_CONFIG_ID,
overrides))
The configuration looks fine on return. However, launching new crawls with a
REST-modified configuration does not use the requested override. I confirmed
that I can override this from the file configuration.
I currently don't have any way from the Nutch interface to disambiguate
messages coming from different crawls.
> 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
> Labels: memex
> Fix For: 1.12
>
> Attachments: NUTCH-2132.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)
