Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <278847.93351293911506943.JavaMail.jira@thor>
Date: Sat, 1 Jan 2011 14:51:46 -0500 (EST)
From: "fabrizio giustina (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-2622) Index analizers that extends
 StandardAnalyzer need to implement reusableTokenStream() since jackrabbit
 2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

fabrizio giustina updated JCR-2622:
-----------------------------------

    Resolution: Not A Problem
        Status: Resolved  (was: Patch Available)

> Index analizers that extends StandardAnalyzer need to implement reusableT=
okenStream() since jackrabbit 2.1
> -------------------------------------------------------------------------=
---------------------------------
>
>                 Key: JCR-2622
>                 URL: https://issues.apache.org/jira/browse/JCR-2622
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.2.0
>            Reporter: fabrizio giustina
>            Priority: Critical
>         Attachments: JCR-2622-tests_and_patch.diff
>
>
> I just tried migrating an existing project which was using jackrabbit 2.0=
.0 to 2.1.0.
> We have an index analyzer configured which filters accented chars:=20
> {code}
> public class ItalianSnowballAnalyzer extends StandardAnalyzer
> {
>     @Override
>     public TokenStream tokenStream(String fieldName, Reader reader)
>     {
>         return new ISOLatin1AccentFilter(new LowerCaseFilter((super.token=
Stream(fieldName, reader))));
>     }
> }
> {code}
> The project has a good number of unit tests, an xml is loaded in a memory=
-only jackrabbit repository and several queries are checked against expecte=
d results.
> After migrating to 2.1.0 none of the tests that relied on the Index anali=
zer work anymore, for example searching for "test" doesn't find anymore nod=
es containing "t=C3=A8st".
> Upgrading to jackrabbit 2.1.0 is the only change done (no changes in the =
configuration/code or other libraries at all). Rolling back to the 2.0.0 de=
pendency is enough to make all the tests working again.
> I've checked the changes in 2.1 but I couldn't find any apparently relate=
d change. Also note that I was already using the patch in JCR-2504 also bef=
ore (configuration loading works fine in the unpatched 2.1). Another point =
is that the configured IndexAnalyzer still gets actually called during our =
tests (checked in debug mode).
> Any idea?

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.