Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Sun, 29 Sep 2013 03:51:26 +0000 (UTC)
From: "frank (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12668985.1379415352125.269.1380426686522@arcas>
In-Reply-To: <JIRA.12668985.1379415352125@arcas>
References: <JIRA.12668985.1379415352125@arcas>
Subject: [jira] [Comment Edited] (JCR-3667) Possible regression with
 accepted content types when extracting and indexing binary values
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-3667?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137812=
33#comment-13781233 ]=20

frank edited comment on JCR-3667 at 9/29/13 3:50 AM:
-----------------------------------------------------

http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-parent/pom.xml
change tika.version property to:

<tika.version>1.4</tika.version>


was (Author: surfie):
http://svn.apache.org/repos/asf/jackrabbit/tags/2.6.3/jackrabbit-parent/pom=
.xml
change tika.version property to:

<tika.version>1.4</tika.version>

> Possible regression with accepted content types when extracting and index=
ing 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=C3=A9dric Damioli
>              Labels: patch
>             Fix For: 2.4.5, 2.6.4, 2.7.2
>
>
> 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 extrac=
ted and indexed because the XMLParser does not declare "text/xml" as a supp=
orted type.
> The problem here is that there is a regression between 2.4.3 and 2.4.4, b=
ecause the same content was previously well recognized by Tika's Detector a=
nd then extracted.
> Furthermore, it seems to me inconsistent on one hand to rely on the decla=
red content type and on the other hand to delegate the actual type detectio=
n to Tika ?=20
> This may lead to cases where the jcr:mimeType value is set to eg. "applic=
ation/pdf" but detected and parsed by Tika as "text/plain" with no error.


--
This message was sent by Atlassian JIRA
(v6.1#6144)