You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2014/09/25 04:18:34 UTC
[jira] [Created] (NUTCH-1854) ./bin/crawl fails with a parsing
fetcher
Lewis John McGibbney created NUTCH-1854:
-------------------------------------------
Summary: ./bin/crawl fails with a parsing fetcher
Key: NUTCH-1854
URL: https://issues.apache.org/jira/browse/NUTCH-1854
Project: Nutch
Issue Type: Bug
Components: parser
Affects Versions: 1.9
Reporter: Lewis John McGibbney
Fix For: 1.10
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" java.io.IOException: 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
(v6.3.4#6332)