[
https://issues.apache.org/jira/browse/NUTCH-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547425#comment-14547425
]
Hudson commented on NUTCH-1854:
-------------------------------
SUCCESS: Integrated in Nutch-trunk #3125 (See
[https://builds.apache.org/job/Nutch-trunk/3125/])
Re-apply NUTCH-1854 after mistakenly rolled back during NUTCH-1973. (mattmann:
http://svn.apache.org/viewvc/nutch/trunk/?view=rev&rev=1679911)
* /nutch/trunk/src/java/org/apache/nutch/parse/ParseSegment.java
* /nutch/trunk/src/java/org/apache/nutch/segment/SegmentChecker.java
> ./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
> Assignee: Sebastian Nagel
> Labels: memex
> Fix For: 1.10
>
> Attachments: NUTCH-1854ver1.patch, NUTCH-1854ver2.patch,
> NUTCH-1854ver3.patch, NUTCH-1854ver4.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" 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)
