You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Markus Jelsma (JIRA)" <ji...@apache.org> on 2011/08/31 14:55:10 UTC
[jira] [Updated] (NUTCH-1102) Fetcher, rely on fetcher.parse
directive only
[ https://issues.apache.org/jira/browse/NUTCH-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Jelsma updated NUTCH-1102:
---------------------------------
Patch Info: [Patch Available]
Assignee: Markus Jelsma
Summary: Fetcher, rely on fetcher.parse directive only (was: Fetcher -noParse | -parse switches)
I've a patch but it also includes code from NUTCH-1067. I'd prefer to include both patches at once.
Julien, any sight on progress with 1067?
Cheers
> Fetcher, rely on fetcher.parse directive only
> ---------------------------------------------
>
> Key: NUTCH-1102
> URL: https://issues.apache.org/jira/browse/NUTCH-1102
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 1.3
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Priority: Minor
> Fix For: 1.4
>
>
> The fetcher in 1.3 still has the -noParse option but does not do anything. A -parse switch (NUTCH-872) is ignored, it seems my build wasn't messed up afterall. The fetcher.parse configuration directive is also ignored. In short, Nutch 1.3 cannot parse fetched data immediately regardless of configuration and options.
> How to procede? It makes little sense to have both the command option and the configuration directive, it raises the question of authority and adds unnecessary confusion.
> I propose to get rid of the command option and rely on the configuration directive alone.
> Please comment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira