You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Sebastian Nagel (JIRA)" <ji...@apache.org> on 2018/06/13 07:09:00 UTC
[jira] [Assigned] (NUTCH-1993) Nutch does not use backup parsers
[ https://issues.apache.org/jira/browse/NUTCH-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Nagel reassigned NUTCH-1993:
--------------------------------------
Assignee: Sebastian Nagel (was: Chris A. Mattmann)
> Nutch does not use backup parsers
> ---------------------------------
>
> Key: NUTCH-1993
> URL: https://issues.apache.org/jira/browse/NUTCH-1993
> Project: Nutch
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.13
> Reporter: Arkadi Kosmynin
> Assignee: Sebastian Nagel
> Priority: Major
> Fix For: 1.15
>
> Attachments: NUTCH-1193.patch
>
>
> From reading the code it is clear that it is designed to allow using several parsers to parse a document in a sequence, until it is successfully parsed. In practice, this does not work because these lines
> if (parseResult != null && !parseResult.isEmpty())
> return parseResult;
> break the loop even if the parsing has failed because parseResult is not empty anyway, it contains a ParseData with ParseStatus.FAILED.
> A fix:
> if ( parseResult.isAnySuccess() )
> return parseResult;
> Where parseResult.isAnySuccess() returns true if any of the parsing attempts were successful.
> This fix is important because it allows use of backup parsers as originally designed and thus increase index completeness.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)