[
https://issues.apache.org/jira/browse/NUTCH-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487035#comment-14487035
]
Sebastian Nagel commented on NUTCH-1854:
----------------------------------------
Definitely: fetcher.store.content=false and fetcher.parse=false are mutually
exclusive in "normal" crawler work-flows. There are others where this
combination makes sense, e.g., check availability of URLs, do network load
tests, etc. I don't think we can make the work-flow (bin/crawl) safe from any
misconfigurations, at least, when it's about manually editing properties (would
be different with a config GUI). It's important to provide meaningful messages
for common errors (cf. NUTCH-1370 if seeds are excluded by URL filters).
+1 for skipping already parsed segments does not harm but
* message that parsing segment is skipped should be a warning - it's still a
misconfiguration!
* the "finished at ..., elapsed ..." message is misleading if a segment is
skipped
* ev. add the checking code to SegmentChecker (NUTCH-1771)
> ./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: 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" 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)
