[
https://issues.apache.org/jira/browse/NUTCH-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549957#comment-14549957
]
Sujen Shah commented on NUTCH-2011:
-----------------------------------
Thanks for sharing the plugin link will look into it.
I did not quite understand by what you meant to ask in
"Is there an alternative to store the information persistently in existing data
structures? An in-memory FetchNodeDb will disappear as soon a fetcher task is
finished."
Is this what you suggest - Make modifications in the CrawlDb to store extra
variable/s to support creation of a tree and store "round number". And, use the
FetchNodeDb only for real-time info and make it disappear after completion of
the fetch task.
Since the CrawlDb is updated at the end of the crawl cycle, FetchNodeDb could
serve real-time data and CrawlDb could serve "past" data.
> Endpoint to support realtime JSON output from the fetcher
> ---------------------------------------------------------
>
> Key: NUTCH-2011
> URL: https://issues.apache.org/jira/browse/NUTCH-2011
> Project: Nutch
> Issue Type: Sub-task
> Components: fetcher, REST_api
> Reporter: Sujen Shah
> Assignee: Chris A. Mattmann
> Labels: memex
> Fix For: 1.11
>
>
> This fix will create an endpoint to query the Nutch REST service and get a
> real-time JSON response of the current/past Fetched URLs.
> This endpoint also includes pagination of the output to reduce data transfer
> bw in large crawls.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
