[
https://issues.apache.org/jira/browse/NUTCH-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549311#comment-16549311
]
Hudson commented on NUTCH-1993:
-------------------------------
SUCCESS: Integrated in Jenkins build Nutch-trunk #3547 (See
[https://builds.apache.org/job/Nutch-trunk/3547/])
NUTCH-1993 Nutch does not use backup parsers - apply patch contributed (snagel:
[https://github.com/apache/nutch/commit/b88930e4f1a5f6178a55123379d7f976b4b8d81a])
* (edit) src/java/org/apache/nutch/parse/ParseResult.java
* (edit) src/java/org/apache/nutch/parse/ParseUtil.java
> 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)
