nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <>
Subject [jira] [Commented] (NUTCH-1854) ./bin/crawl fails with a parsing fetcher
Date Tue, 07 Apr 2015 02:03:12 GMT


Lewis John McGibbney commented on NUTCH-1854:

Hi Chris

I saw this and it looks nice. Looks like it will make it in to the codebase
reasonably soon!
The main point I am making is that a failed parsing fetcher, in my own
experience, is a primary factor behind corrupt segments. I therefore make
best efforts to avoid this practice.

It looks like Asitang has a better solution e.g. Most recent patch

Ack and a +1 on top


> ./bin/crawl fails with a parsing fetcher
> ----------------------------------------
>                 Key: NUTCH-1854
>                 URL:
>             Project: Nutch
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.9
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>             Fix For: 1.11
>         Attachments: NUTCH-1854ver1.patch
> If you run ./bin/crawl with a parsing fetcher e.g.
> <property>
> >   <name>fetcher.parse</name>
> >   <value>false</value>
> >   <description>If true, fetcher will parse content. Default is false,
> > which means
> >   that a separate parsing step is required after fetching is
> > finished.</description>
> > </property>
> we get a horrible message as follows
> Exception in thread "main" Segment already parsed!
> We could improve this by making logging more complete and by adding a trigger to the
crawl script which would check for crawl_parse for a given segment and then skip parsing if
this is present.

This message was sent by Atlassian JIRA

View raw message