nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Nagel (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (NUTCH-1854) ./bin/crawl fails with a parsing fetcher
Date Mon, 13 Apr 2015 11:25:13 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492286#comment-14492286
] 

Sebastian Nagel edited comment on NUTCH-1854 at 4/13/15 11:24 AM:
------------------------------------------------------------------

Thanks, [~asitang]!
* NUTCH-1771 is committed, can you "rebase" the patch?
* for clarity and brevity I would prefer to implement an explicit check "isParsed" in SegmentChecker
and call it immediately at the beginning of the parse function, e.g.:
{code}
 public void parse(Path segment) throws IOException {
  if (SegmentChecker.isParsed(segment, FileSystem.get(getConf())) {
   LOG.warn("...");
   return;
  }
{code}


was (Author: wastl-nagel):
Thanks, [~asitang]!
* NUTCH-1771 is committed, can you "rebase" the patch
* for clarity and brevity I would prefer to implement an explicit check "isParsed" in SegmentChecker
and call it immediately at the beginning of the parse function, e.g.:
{code}
 public void parse(Path segment) throws IOException {
  if (SegmentChecker.isParsed(segment, FileSystem.get(getConf())) {
   LOG.warn("...");
   return;
  }
{code}

> ./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, NUTCH-1854ver2.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)

Mime
View raw message