nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-1102) Fetcher, rely on fetcher.parse directive only
Date Wed, 02 Nov 2011 11:13:32 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142051#comment-13142051
] 

Hudson commented on NUTCH-1102:
-------------------------------

Integrated in Nutch-nutchgora #55 (See [https://builds.apache.org/job/Nutch-nutchgora/55/])
    NUTCH-1191 Port NUTCH-1102 to nutchgora - consistent use of fetcher.parse

ferdy : http://svn.apache.org/viewvc/nutch/branches/nutchgora/viewvc/?view=rev&root=&revision=1196516
Files : 
* /nutch/branches/nutchgora/CHANGES.txt
* /nutch/branches/nutchgora/src/java/org/apache/nutch/crawl/Crawler.java
* /nutch/branches/nutchgora/src/java/org/apache/nutch/fetcher/FetcherJob.java
* /nutch/branches/nutchgora/src/java/org/apache/nutch/metadata/Nutch.java
* /nutch/branches/nutchgora/src/java/org/apache/nutch/tools/Benchmark.java

                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message