Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Mon, 6 May 2013 11:14:16 +0000 (UTC)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12630858.1360064158766.272994.1367838856009@arcas>
In-Reply-To: <JIRA.12630858.1360064158766@arcas>
References: <JIRA.12630858.1360064158766@arcas>
Subject: [jira] [Updated] (JCR-3511) JackrabbitQueryParser incorrectly
 handles terms with wildcards when using analyzers that do more than
 lowercasing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-3511?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-3511:
-------------------------------

    Fix Version/s:     (was: 2.2.14)
                       (was: 2.4.4)
   =20
> JackrabbitQueryParser incorrectly handles terms with wildcards when using=
 analyzers that do more than lowercasing=20
> -------------------------------------------------------------------------=
-----------------------------------------
>
>                 Key: JCR-3511
>                 URL: https://issues.apache.org/jira/browse/JCR-3511
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: Ard Schrijvers
>            Assignee: Ard Schrijvers
>
> wildcard pre/postfixing combined with stemming is not always possible to =
work correctly in Lucene. However, postfixing a term with a wildcard should=
 play nicely with the configured analyzers. Assume you have an analyzer tha=
t contains Lucene ISOLatin1AccentFilter. In that case, there is currently t=
he problem that when for example indexing the word 'tr=C3=A8s' (mind the =
=C3=A8 accent) and then quering=20
> //*[jcr:contains(.',tr=C3=A8*')] does not have a hit for tr=C3=A8s.=20
> //*[jcr:contains(.',tr=C3=A8s')] DOES and
> //*[jcr:contains(.',tr*')] DOES but
> //*[jcr:contains(.',tr=C3=A8*')] DOES NOT
> Problem is simple to solve as in JackrabbitQueryParser#getWildcardQuery g=
ets the non-analyzed termStr as argument where afaics it should get the ana=
lyzed version. Then, also  getLowercaseExpandedTerms() in #getWildcardQuery=
 is redundant

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira