nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Nagel (JIRA)" <>
Subject [jira] [Commented] (NUTCH-2011) Endpoint to support realtime JSON output from the fetcher
Date Mon, 18 May 2015 10:38:00 GMT


Sebastian Nagel commented on NUTCH-2011:

??about modifying the CrawlDb to hold one more parameter which is the round number?? that
would be easy to achieve without any modifications of CrawlDb: add the depth (in rounds/cycles)
to CrawlDatum's meta data (cf. the plugin [scoring-depth|]
doing this for the depth in terms of links needed to reach a document starting from one of
the seeds). It should be also possible to store one predecessor (one must be enough if a tree
is assumed) for each item in the CrawlDb - it's then possible to span up the tree by reading
the CrawlDb.
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.

> Endpoint to support realtime JSON output from the fetcher
> ---------------------------------------------------------
>                 Key: NUTCH-2011
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message