Can some one pls help with the logic that can be applied to decide on the
closeness requirement given below (like 50% matching). This matching is a
pure text matching.
Since the current lucene score does not translate into the percentage of
closeness, is there anything else that can give this info
Hi
No success yet to resolve this. Anyone knows where can be the problem?
Thanks in advance,
Jose García
On Wed, Aug 24, 2011 at 5:29 PM, jose garcia wrote:
> Hi
>
> I'm having some issues with queries using different fuzziness values and
> StandardAnalyzer for a field:
>
> 1) *+any:climate~0.
Bernd,
Glad you like the site. Please do let me know if you have any suggestions
for the site.
You will need to login to (a) post content, (b) vote and help refine the
quality of content on the site, and (c) to subscribe to the group and be
notified when someone uploads content.
We also have an I
Thanks I will give this a try, seems like it should work for my case.
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Tuesday, August 30, 2011 3:53 PM
To: java-user@lucene.apache.org
Subject: RE: No subsearcher in Lucene 3.3?
Hi,
Use ReaderUtil from o.a.l.util pac
