[
https://issues.apache.org/jira/browse/NUTCH-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192997#comment-13192997
]
Julien Nioche commented on NUTCH-1258:
--------------------------------------
What about using a similar mechanism for the parameters as we do for the lang
extraction
{noformat}
<name>lang.extraction.policy</name>
<value>detect,identify</value>
{noformat}
and specify explicitly the order in which we should get the data from e.g.
{noformat}
<name>moreIndexingFilter.mimeTypeSource</name>
<value>parse,content</value>
{noformat}
or
{noformat}
<name>moreIndexingFilter.mimeTypeSource</name>
<value>parse</value>
{noformat}
if we don't want the content at all
> MoreIndexingFilter should be able to read Content-Type from both parse
> metadata and content metadata
> ----------------------------------------------------------------------------------------------------
>
> Key: NUTCH-1258
> URL: https://issues.apache.org/jira/browse/NUTCH-1258
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Affects Versions: 1.4
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.5
>
> Attachments: NUTCH-1258-1.5-1.patch
>
>
> The MoreIndexingFilter reads the Content-Type from parse metadata. However,
> this usually contains a lot of crap because web developers can set it to
> anything they like. The filter must be able to read the Content-Type field
> from content metadata as well because that contains the type detected by
> Tika's Detector.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
