[
https://issues.apache.org/jira/browse/NUTCH-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki closed NUTCH-413.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
> Fetcher ignores -noParsing command line option
> ----------------------------------------------
>
> Key: NUTCH-413
> URL: https://issues.apache.org/jira/browse/NUTCH-413
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 0.8.1
> Environment: Fedora Core 6, nutch 0.8.1
> Reporter: Jonathan Amir
> Fix For: 1.0.0
>
>
> I believe that the patch applied in NUTCH-337 broke the fetcher. Now the
> fetcher ignores the -noParsing command-line option - the parsing occurs
> anyway.
> To the best of my understanding of nutch, I managed to trace the problem as
> follows in the code:
> In fetcher class, in line 473, -noParsing is evaluted properly and placed
> into a Configuration created by NutchConfiguartion.create(). So far so good.
> In the same file, in line 280, the decision whether to parse or not depends
> on local field "parsing". During execution, this fields value is true,
> instead of false. This field is set to true by method "configure", in line
> 357. The problem is that method "configure" accepts a JobConf as a parameter,
> but the actual JobConf object that is passed to it is not the one used
> previously in line 473.
> The one that is actually passed to configure is a different object. I think
> it is created in line 422, but I am not sure about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
