I would recommend upgrading Lucene to at least 2.9.4. Your version is very
antique.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Donld Hill [mailto:dh...@eweb-service.com]
> Sent: Thursday, December 16
More likely to be a bug in your code rather than in lucene. I suggest
you post the smallest possible self-contained program or test case
that demonstrates the problem.
--
Ian.
On Thu, Dec 16, 2010 at 1:56 AM, Mike Cawson wrote:
> I'm using MultiPhraseQuery to implement a fuzzy phrase query.
>
>
> > I have a app that seems to be locking on some search calls. I am
> including
> > the stacktrace for the blocked and blocker thread.
>
Is it daedlock for sure?
No search deadlock fixes were done since 2.1.0, so perhaps it is something
else...
> "TP-Processor177" daemon prio=10 tid=0x00
On Thu, 2010-12-16 at 06:59 +0100, Ganesh wrote:
> 250 GB of data, 40 GB of Index Size, 60 million records is
> working fine with 1 GB RAM. We are storing minmal amount
> of data in index. We are doing sorting on Date. Even in
> single system, the database are shard.
Looking back in the list, I se
So will updating to a newer version of Lucene help with the
performance when loading DOCS. I will also do some research to see what
is being loaded as this is a 3rd party that's using Lucene.
Can I safely upgrade to a newer version, do I need to perform any
updates on the actual indices?
On
On Thu, Dec 16, 2010 at 8:36 AM, Donld Hill wrote:
> Can I safely upgrade to a newer version, do I need to perform any updates on
> the actual indices?
>From my personal experience, upgrading from v2 to v3 required rebuilds
of indices since we experienced some problems performing queries
against
Hi,
LuSqlv2 beta comes out in the next few weeks, and is designed to
address this issue (among others).
LuSql original
(http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/LuSql
now moved to: https://code.google.com/p/lusql/) is a JDBC-->Lucene
high performance loader.
You may have se
Hello All,
I'm new to lucene, and i'm confronted with an input/output error exception
listed as below.
As designed, I have one machine writing to an index stored on an NFS mount, and
other machine(s)
reading (and periodically re-opening the index).
I use a thread to maintain all the IndexSear
