nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Johnson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-1917) index.parse.md, index.content.md and index.db.md should support wildcard
Date Tue, 18 Oct 2016 22:44:58 GMT

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

David Johnson commented on NUTCH-1917:
--------------------------------------

I've generated a patch for Index-metadata to allow for a wildcard in index.parse.md. (Nutch
version 1.11)
Effectively, placing a * as an element in the list will enable the new behavior.

PLEASE DO NOT USE THIS SETTING UNLESS YOU KNOW WHAT YOU ARE DOING!!!!!!
This setting has the potential to create a huge number of single entry fields; depending on
the index configuration of your search system, this could be incredibly detrimental to performance
and even affect stability.

> index.parse.md, index.content.md and index.db.md should support wildcard
> ------------------------------------------------------------------------
>
>                 Key: NUTCH-1917
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1917
>             Project: Nutch
>          Issue Type: Bug
>          Components: indexer
>    Affects Versions: 1.9
>            Reporter: Lewis John McGibbney
>         Attachments: MetadataIndexer.java.patch
>
>
> Right now metatags.names supports the '*' character for a catch all.
> I believe that the above index properties should also support catch all as a mechanism
for quickly building augmented data models from crawl data. Individual identification and
manual inclusion of tags one by one is error prone and time consuming.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message