You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@nutch.apache.org by "Markus Jelsma (Commented) (JIRA)" <ji...@apache.org> on 2012/01/25 13:00:42 UTC

[jira] [Commented] (NUTCH-1258) MoreIndexingFilter should be able to read Content-Type from both parse metadata and content metadata

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

Markus Jelsma commented on NUTCH-1258:
--------------------------------------

Comments? Tested and things work as expected, tests pass. Ill commit shortly unless there are objections.
                
> 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