[jira] [Resolved] (OAK-6587) Provide a way to "force" Tika to treat binaries with a different mime type than the jcr:mimeType property

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-6587.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.7

> Provide a way to "force" Tika to treat binaries with a different mime type than the jcr:mimeType property
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: OAK-6587
>                 URL: https://issues.apache.org/jira/browse/OAK-6587
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Justin Edelson
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8, 1.7.7
>
>
> There are occasions when an existing Tika parser can be used to parse a binary, but Tika doesn't "think" it can because the mime type isn't in the Parser's list of supported types. There appears to be no way to configure this in Tika. Editing the config.xml file only allows for types which are _theoretically_ parseable to be mapped to different parsers; it doesn't change the set of supported types.
> To deal with this, I'd like to add a new configuration node structure named {{mimeTypes}} under the {{tika}} node of lucene indexes. Using this structure, a mapped type can be defined and this type will be used for interaction with Tika.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)