[
https://issues.apache.org/jira/browse/NUTCH-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894505#action_12894505
]
Julien Nioche edited comment on NUTCH-868 at 8/2/10 5:35 AM:
-------------------------------------------------------------
ParseUtil could return null before NUTCH-696, it's just that it probably did
not happen very often.
According to the javadoc :
{quote}
If the parse is unsuccessful, a message is logged to the <code>WARNING</code>
level, and an empty parse is returned.
{quote}
I will fix ParseUtil so that it returns an empty parse. Since it is called in
various places this will be cleaner than checking that the parse is not null
Thanks
was (Author: jnioche):
ParseUtil could return null before NUTCH-696, it's just that it probably
did not happen very often. I will apply your patch to the trunk, nutchbase and
1.2 and check other places where ParseUtil is called.
Thanks
> ParseSegment NullPointerException
> ---------------------------------
>
> Key: NUTCH-868
> URL: https://issues.apache.org/jira/browse/NUTCH-868
> Project: Nutch
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.2, 2.0, nutchbase
> Environment: Ubuntu 9.10 Linux 2.6.31-14-generic
> Reporter: Max Lynch
> Assignee: Julien Nioche
> Fix For: 1.1, 1.2, 2.0, nutchbase
>
> Attachments: NUTCH-868.patch
>
>
> The Nutch parser step will fail if ParseUtil.parse returns null. Perhaps the
> issue is because I applied this patch:
> https://issues.apache.org/jira/browse/NUTCH-696
> The exception happens in ParseSegment.map at line 91. The attached patch
> fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
