nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lufeng (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (NUTCH-1538) tuning of loaded fields during fetcherJob start-up
Date Tue, 05 Mar 2013 08:26:12 GMT

     [ https://issues.apache.org/jira/browse/NUTCH-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

lufeng updated NUTCH-1538:
--------------------------

    Comment: was deleted

(was: Hi Roland,

Maybe we can add a QueryFieldFilter to remove some field that never used in fetch if fetcher.parse
proerpty is true.)
    
> tuning of loaded fields during fetcherJob start-up
> --------------------------------------------------
>
>                 Key: NUTCH-1538
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1538
>             Project: Nutch
>          Issue Type: Improvement
>          Components: fetcher
>    Affects Versions: 2.1
>         Environment: nutch 2.1 / cassandra 1.2.1 / gora-cassandra 0.2 / gora-core 0.2.1

> running fetch with parse=true
>            Reporter: Roland
>
> Main problem is, nutch is loading nearly every row & column from DB during startup
of a fetcherJob when fetcher.parse=true.
> A parserJob needs e.g. the CONTENT field from db, to parse.
> The fetcherJob adds all fields of the parserJob to it's needed fields, if running with
fetcher.parse=true. [FetcherJob.getFields()]
> If the nutch configuration saves all fetched data to DB (fetcher.store.content=true)
you'll end up loading GBs of unused content during fetcherJob start-up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message