[
https://issues.apache.org/jira/browse/NUTCH-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097953#comment-13097953
]
Markus Jelsma commented on NUTCH-1102:
--------------------------------------
Yes i know. Problem was that there were so many patches for the fetcher at the
same time. Very tricky.
Well, i can, of course, change the code again to rely on the config option
only. The question is, what to do: right now nothing works anyway since the
change of NUTCH-872 broke it, it not compatible with anything right now.
Of course, i prefer not having to rewrite again to support config option only ;)
> 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
>
> Attachments: NUTCH-1102-1.4-1.patch
>
>
> 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
