[
https://issues.apache.org/jira/browse/NUTCH-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593150#comment-13593150
]
Roland commented on NUTCH-1538:
-------------------------------
No, this just happens for the case fetcher.parse=true.
{code}
public Collection<WebPage.Field> getFields(Job job) {
Collection<WebPage.Field> fields = new HashSet<WebPage.Field>(FIELDS);
if (job.getConfiguration().getBoolean(PARSE_KEY, false)) {
ParserJob parserJob = new ParserJob();
fields.addAll(parserJob.getFields(job));
}
[...]
{code}
A 'normal' fetcher should not be affected.
It would be a big improvement to get some kind more granular control which
columns to load. (but it's an improvement, not a bug, I think)
> 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
