[
https://issues.apache.org/jira/browse/NUTCH-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746081#comment-16746081
]
ASF GitHub Bot commented on NUTCH-2686:
---------------------------------------
sebastian-nagel commented on pull request #428: NUTCH-2686 New property:
"moreIndexingFilter.mapMimeTypes.field"
URL: https://github.com/apache/nutch/pull/428#discussion_r248976192
##########
File path: conf/nutch-default.xml
##########
@@ -1207,6 +1207,15 @@
</description>
</property>
+<property>
+ <name>moreIndexingFilter.mapMimeTypes.field</name>
+ <value></value>
+ <description>It's used if moreIndexingFilter.mapMimeTypes is true. Indicates
the field
+ where the mapped MIME-type must be written. If it's null, the field "type"
Review comment:
I would prefer: `If it's empty or unset, the content of the field "type"
..."`
Of course, `conf.get("moreIndexingFilter.mapMimeTypes.field")` returns null
in both cases (empty or unset). But that's only known to programmers familiar
with the internals of a Hadoop configuration. Just to prevent that anybody
writes literally "null" as value.
----------------------------------------------------------------
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:
[email protected]
> 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)
