Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mreutegg@day.com designates
 207.126.148.183 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <813d89dc0908181426r42d160ewe8bfce6b19d02449@mail.gmail.com>
References: <813d89dc0908181426r42d160ewe8bfce6b19d02449@mail.gmail.com>
Date: Thu, 20 Aug 2009 11:31:08 +0200
Message-ID: <a781e7950908200231j212cff9dvabd2c3b28b93fa1a@mail.gmail.com>
Subject: Re: Wrong results from jcr:like query
From: Marcel Reutegger <mreutegg@day.com>
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Tue, Aug 18, 2009 at 23:26, Dan
Diephouse<dan.diephouse@mulesource.com> wrote:
> I have a repository like with the following structure
>
> /hello.wsdl/@name="hello.wsdl"
> /hello.wsdl/1.0/@name="1.0"
>
> I run the query:
>
> //*[jcr:like(fn:lower-case(@name), '%hello.wsdl%')]
>
> This turns into the Lucene query: "+1:name:%hello.wsdl%"
>
> I'm getting back both nodes though, and not just the first one.
>
> I tried both with my forked branch of 1.6/Lucene 2.4.2 (I know, I know....
> just has JCR-977 patches in it) and also with 1.4.x/Lucene 2.2.0 which we
> were on before we upgraded. I can get a more official recent version, but
> does this ring a bell to anyone?

hmm, no. can you please try it with the current trunk and file a jira
issue if the same problem exists there?

thanks

regards
 marcel

> I seem to recall seeing something about it
> at some point.... If you give me an idea of what the modified Lucene query
> should be I can probably provide a patch.
>
> Dan
> --
> Dan Diephouse
> http://mulesource.com | http://netzooid.com/blog
>