Description
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.