You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Marcin Okraszewski (JIRA)" <ji...@apache.org> on 2009/10/08 22:39:31 UTC

[jira] Commented: (NUTCH-677) Segment merge filering based on segment content

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

Marcin Okraszewski commented on NUTCH-677:
------------------------------------------

Sorry, I didn't notice the request for the license header. I've just uploaded files with the header.

> Segment merge filering based on segment content
> -----------------------------------------------
>
>                 Key: NUTCH-677
>                 URL: https://issues.apache.org/jira/browse/NUTCH-677
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 0.9.0
>            Reporter: Marcin Okraszewski
>             Fix For: 1.1
>
>         Attachments: MergeFilter.patch, MergeFilter_for_1.0.patch, SegmentMergeFilter.java, SegmentMergeFilter.java, SegmentMergeFilters.java, SegmentMergeFilters.java
>
>
> I needed a segment filtering based on meta data detected during parse phase. Unfortunately current URL based filtering does not allow for this. So I have created a new SegmentMergeFilter extension which receives segment entry which is being merged and decides if it should be included or not. Even though I needed only ParseData for my purpose I have done it a bit more general purpose, so the filter receives all merged data.
> The attached patch is for version 0.9 which I use. Unfortunately I didn't have time to check how it fits to trunk version. Sorry :(

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.