nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NUTCH-2441) ARG_SEGMENT usage
Date Mon, 04 Dec 2017 06:36:00 GMT


ASF GitHub Bot commented on NUTCH-2441:

okedoki commented on a change in pull request #250: fix for NUTCH-2441 ARG_SEGMENT fix for

 File path: src/java/org/apache/nutch/metadata/
 @@ -96,7 +96,7 @@
 	 * Similar to the -dir command in the bin/nutch script **/
 	public static final String ARG_SEGMENTDIR = "segment_dir";
 	/** Argument key to specify the location of individual segment for the REST endpoints **/
 Review comment:
   @lewismc The motivation is the following : 
   Part of the endpoints treat segments as an individual Path, part as an array of Paths.
Therefore we have an inconsistent usage of the REST API value. The patch allows to use both
of them for all endpoints(either array of paths or an individual path, depends on what you

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:

> -----------------
>                 Key: NUTCH-2441
>                 URL:
>             Project: Nutch
>          Issue Type: Improvement
>          Components: metadata
>    Affects Versions: 1.13
>            Reporter: Semyon Semyonov
>             Fix For: 1.14
>         Attachments: metadataARG_SEGMENT.patch
> The class metadata/  public static final String ARG_SEGMENT = "segment" is
not used correctly. In some cases Fetcher and ParseSegment it is interpreted as a single segmenet,
in others CrawlDb, LinkDb, IndexingJob as an array of segments. Such misunderstanding leads
to inconsistency of usage of the parameter.
> After a discussion with [~wastl-nagel]  the proposed solution is to allow the usage of
both array and a string in all cases. That gives an opportunity to not introduce the broken
> A path is proposed.
>  *The question left is refactoring, all these five components share the same code(two
versions of the same code to be precise). Shouldn't we extract a method and reduce duplicates?

This message was sent by Atlassian JIRA

View raw message