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 (Updated) (JIRA)" <ji...@apache.org> on 2012/01/25 12:46:40 UTC
[jira] [Updated] (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:all-tabpanel ]
Markus Jelsma updated NUTCH-1258:
---------------------------------
Attachment: NUTCH-1258-1.5-1.patch
Patch for 1.5. Adds configuration to read from contentmeta, parsemeta or first parsemeta and fallback to contentmeta (default).
> 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