You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2014/03/14 14:44:43 UTC
[jira] [Updated] (JCR-3667) Possible regression with accepted
content types when extracting and indexing binary values
[ https://issues.apache.org/jira/browse/JCR-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu updated JCR-3667:
---------------------------------
Fix Version/s: (was: 2.7.5)
2.7.6
> Possible regression with accepted content types when extracting and indexing binary values
> ------------------------------------------------------------------------------------------
>
> Key: JCR-3667
> URL: https://issues.apache.org/jira/browse/JCR-3667
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 2.4.4, 2.6.3
> Reporter: Cédric Damioli
> Assignee: Jukka Zitting
> Labels: patch
> Fix For: 2.7.6
>
>
> JCR-3476 introduced a mime-type test before parsing binary values, based on Tika's supported parsers.
> This may lead to incorrect behaviours, with a "text/xml" not being extracted and indexed because the XMLParser does not declare "text/xml" as a supported type.
> The problem here is that there is a regression between 2.4.3 and 2.4.4, because the same content was previously well recognized by Tika's Detector and then extracted.
> Furthermore, it seems to me inconsistent on one hand to rely on the declared content type and on the other hand to delegate the actual type detection to Tika ?
> This may lead to cases where the jcr:mimeType value is set to eg. "application/pdf" but detected and parsed by Tika as "text/plain" with no error.
--
This message was sent by Atlassian JIRA
(v6.2#6252)