Thanks very much, this is very helpful!
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent: Saturday, June 30, 2012 2:48 PM
To: java-user@lucene.apache.org
Subject: RE: Lucene indexed data corruption error
See this issue: https://issues.apache.org/jira/browse/LUCENE-29
See this issue: https://issues.apache.org/jira/browse/LUCENE-2975
It's not quite clear, which versions of Java are affected by this. I can only
say for sure, that everything <=1.6.0_18 is fine and working again in _29
(official Oracle/Sun JDKs only). OpenJDK versions shipped with various Linux
You didn't show us your "luceneQuery", but the gist of the solution is to
use MUST clauses for each of the individual terms and then a SHOULD of the
phrase. You can add an additional boost to the phrase, but lucene should
naturally boost documents containing the phrase.
-- Jack Krupansky
Hi Ume,
I read your blog, only issue is that we are using java 1.6 as indicated below,
have we ever heard of similar issue in java 1.6 ?
Two facts:
1) we are using gluster to replicate data into another folder (so that we have
a back up for fault tolerance), the replication is going on continuous
Thanks for such a quick help!
The java we use is:
java -version
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.13) (6b20-1.9.13-0ubuntu1~10.04.1)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
Best regards, Lisheng
-Original Message-
From: Uwe Schindler [mailto:
Hi,
Suppose we have a query "balcony table". I want results to be returned by
exact match (first priority) and by single words matching as well (for
"balcony" or for "table"). So currently my solution is:
Analyzer analyzer = new SnowballAnalyzer("English",
StopAnalyzer.ENGLISH_STOP_WORDS_SET);
What JVM are you using? This looks like one of the Vint bugs we found in recent
Oracle Java versions, where we have workarounds since Lucene 3.1. See my blog
post about the Java 7 bugs, too, they are closely related: blog.thetaphi.de
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.
Hi,
We have been using lucene 2.3.2 for years well (yes, we should upgrade).
Recently we encountered data corruption error when commiting IndexWriter:
///
background merge hit exception: _14b:c61262 _1ag:c11225 _1gb:c9411 _1gv:c905
_1gw:c50 _1gx:c50 _1gy:c50 _1gz:c50 _1h0:c31 into _1h1 [opti
It hasn't been committed yet ... it's a patch on
https://issues.apache.org/jira/browse/LUCENE-4123
Mike McCandless
http://blog.mikemccandless.com
On Sat, Jun 30, 2012 at 4:24 AM, Cheng wrote:
> Hi,
>
> I can't find the CachingRAMDirectory in Lucene 3.6. Is this decaperated?
>
> Thanks
>
> On
Hi,
I can't find the CachingRAMDirectory in Lucene 3.6. Is this decaperated?
Thanks
On Mon, Jun 18, 2012 at 7:32 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> 9 fold improvement using RAMDir over MMapDir is much more than I've
> seen (~30-40% maybe) in the past.
>
> Can you exp
10 matches
Mail list logo
