You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/16 13:49:00 UTC

[jira] [Commented] (NUTCH-2686) Separate field for mime types mapped by index-more plugin

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

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

r0ann3l commented on pull request #428: NUTCH-2686 New property: "moreIndexingFilter.mapMimeTypes.field"
URL: https://github.com/apache/nutch/pull/428
 
 
   Includes a new property: "moreIndexingFilter.mapMimeTypes.field", which indicates the field's name where the mapped mime type must be written. If this property is NULL (default value) the field "type" will be replaced by the mapped mime type (current behavior).
 
----------------------------------------------------------------
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:
users@infra.apache.org


> Separate field for mime types mapped by index-more plugin
> ---------------------------------------------------------
>
>                 Key: NUTCH-2686
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2686
>             Project: Nutch
>          Issue Type: Improvement
>          Components: indexer
>    Affects Versions: 1.15
>            Reporter: Roannel Fernández Hernández
>            Assignee: Roannel Fernández Hernández
>            Priority: Minor
>             Fix For: 1.16
>
>
> Since [NUTCH-1262|https://issues.apache.org/jira/browse/NUTCH-1262], several mime types can be mapped to a different value. By default, the behavior is to replace the original value with the new one. But if we want to keep the original mime type too? This issue pretends to accomplish this requirement.



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