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

ASF GitHub Bot commented on NUTCH-2012:
---------------------------------------

sebastian-nagel opened a new pull request #310: NUTCH-2012 Merge parsechecker 
and indexchecker
URL: https://github.com/apache/nutch/pull/310
 
 
   - let ParserChecker inherit from AbstractChecker
     (URLs are now read from stdin resp. parsechecker listens on the given port)
   - sync run() method of classes ParserChecker and IndexingFiltersChecker
   - redirects are followed with command-line option -followRedirects
   - adds option -normalize to ParserChecker (fixes NUTCH-2145/NUTCH-2554)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Merge parsechecker and indexchecker
> -----------------------------------
>
>                 Key: NUTCH-2012
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2012
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 1.10
>            Reporter: Sebastian Nagel
>            Priority: Minor
>
> ParserChecker and IndexingFiltersChecker have evolved from simple tools to 
> check parsers and parsefilters resp. indexing filters to powerful tools which 
> emulate the crawling of a single URL/document:
> - check robots.txt (NUTCH-2002)
> - follow redirects (NUTCH-2004)
> Keeping both tools in sync takes extra work (cf. NUTCH-1757/NUTCH-2006, also 
> NUTCH-2002, NUTCH-2004 are done only for parsechecker). It's time to merge 
> them
> * either into one general debugging tool, keeping parsechecker and 
> indexchecker as aliases
> * centralize common code in one utility class



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to