Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B69FE105B8 for ; Tue, 5 Nov 2013 09:22:29 +0000 (UTC) Received: (qmail 4676 invoked by uid 500); 5 Nov 2013 09:22:27 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 4402 invoked by uid 500); 5 Nov 2013 09:22:22 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 4368 invoked by uid 99); 5 Nov 2013 09:22:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Nov 2013 09:22:19 +0000 Date: Tue, 5 Nov 2013 09:22:19 +0000 (UTC) From: "Alex Parvulescu (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3667?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Parvulescu updated JCR-3667: --------------------------------- Fix Version/s: (was: 2.7.2) 2.7.3 > 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 > Assignee: Jukka Zitting > Labels: patch > Fix For: 2.7.3 > > > 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)